Removing your organization's logo from Zoho Desk is a straightforward API operation that sends a single DELETE request to the organization logo endpoint — no request body required.
Why this matters
If your company rebrands, merges, or simply needs to reset its Zoho Desk portal to a clean state, you may need to programmatically remove the existing logo. This is also useful in automated deployment pipelines where environment-specific branding must be cleared before a new logo is uploaded. Understanding the correct endpoint prevents accidental deletion of related assets such as the favicon or department logos, which live on separate routes.
> Note: Beam Help is an independent Zoho consultancy — not official Zoho support. The steps below are based on the Zoho Desk REST API.
---
Step-by-step
Step 1. Confirm you have the correct OAuth scopes in place before making any call. At minimum your token should include Desk.basic.READ and Desk.settings.ALL (or the relevant Desk.settings.DELETE scope) so the API accepts the request. [4]
Step 2. Retrieve your organization_id. If you do not already have it stored, call the organizations list endpoint and pull the id field from the first item in the returned data array. Your integration layer should cache this value to avoid repeated lookups. [7]
Step 3. Issue a DELETE request to the organization logo endpoint:
DELETE /api/v1/organizations/{organization_id}/logo
Replace {organization_id} with the numeric or string ID obtained in Step 2. No request body is needed. [1]
In Python, using the Zoho Desk client wrapper, the call looks like this:
response = desk_api.delete_organization_logo(organization_id="YOUR_ORG_ID")
A successful response indicates the logo has been removed from the organization. [1]
Step 4. Verify the deletion by navigating to your Zoho Desk portal settings, or by calling the organization details endpoint and confirming the logo field is empty or null.
---
Common pitfalls
- Wrong endpoint for department logos. The organization logo endpoint and the department logo endpoint are distinct. If you need to remove a logo tied to a specific department rather than the whole organization, use
DELETE /api/v1/departments/{departmentid}/logowith the relevantdepartmentidinstead. [2]
- Favicon vs. logo confusion. The organization favicon is managed separately at
DELETE /api/v1/organizations/{organization_id}/favicon. Sending a delete to the logo route will not affect the favicon, and vice versa. [3]
- Re-uploading after deletion. If you need to replace rather than permanently remove the logo, use
POST /api/v1/organizations/{organization_id}/logowith the new image data. Deleting first is not required — aPOSTto that endpoint will overwrite the existing logo directly. [8]
- Missing or expired OAuth token. If the access token has expired, the request will be rejected. Ensure your integration refreshes the token before making the call, using the stored
refreshtokento obtain a newaccesstoken. [7]
---
What to check
- Scope coverage: Confirm your OAuth token includes the necessary
Desk.settingsscopes so theDELETEcall is authorized. [4] - Correct ID in the path: Double-check that the
organization_idin the URL matches your actual Zoho Desk organization, not a department ID or a CRM organization ID. [^1, ^7] - Asset type targeted: Verify you are hitting the
/logopath and not/faviconif your goal is specifically the organization logo. [3]