How to delete organization favicon in Zoho Desk

Removing your organization's favicon in Zoho Desk is done via a single authenticated API call that targets the favicon resource for your specific organization. Here's everything you need to make it work cleanly.

Why this matters

Your Zoho Desk portal displays a favicon in browser tabs and bookmarks, reinforcing your brand identity. If you're rebranding, cleaning up a test environment, or simply resetting to the Zoho Desk default, you'll need to programmatically delete the existing favicon. This is especially relevant for admins managing multiple organizations or automating environment teardowns via scripts.

Step-by-step

Step 1. Confirm your Organization ID.

Before making any API call, locate your organization_id. This is the unique identifier for your Zoho Desk organization and is required as a path parameter in every organization-level request. You can retrieve it from your Zoho Desk admin settings or by calling the organizations endpoint. ^[1]

Step 2. Verify your OAuth scopes.

Your API client must be authorized with the appropriate Zoho Desk scopes. At minimum, ensure your token includes Desk.settings.DELETE or a broader Desk.settings.ALL scope, since favicon management falls under organization settings. Without the correct scope, the API will reject your request. ^[7]

Step 3. (Optional) Confirm a favicon exists first.

Before issuing a delete, it's good practice to check whether a favicon is currently set. Send a GET request to the following endpoint:

GET /api/v1/organizations/{organization_id}/favicon

If the response returns a favicon resource, proceed to deletion. If nothing is set, the delete call may return an error or a no-op response. ^[4]

Step 4. Send the DELETE request.

Issue a DELETE request to the favicon endpoint, substituting your real organization ID:

DELETE /api/v1/organizations/{organization_id}/favicon

This is the dedicated operation (deleteorganizationfavicon) for removing the favicon tied to your organization. ^[1]

Step 5. Implement using the Python client (if applicable).

If you're using a Python-based API wrapper, the call looks like this:

def delete_organization_favicon(self, organization_id: str, p: dict = None):
    return self.c.request("DELETE", f"/api/v1/organizations/{organization_id}/favicon", p, None)

Pass your organization_id as a string. The optional p parameter can carry any additional query parameters your environment requires. ^[1]

Step 6. Confirm deletion.

After a successful response, repeat the GET /api/v1/organizations/{organization_id}/favicon call from Step 3. The favicon resource should no longer be present, confirming the deletion was successful. ^[4]

---

> Note from Beam Help: We are independent expert support for Zoho — not official Zoho support. If you encounter account-level restrictions or billing-related blocks, please contact Zoho directly.

---

Common pitfalls

• Wrong endpoint for logos vs. favicons. The favicon endpoint (/favicon) and the logo endpoint (/logo) are separate resources. Calling DELETE /api/v1/organizations/{organization_id}/logo removes the organization logo, not the favicon — make sure you're targeting the right path. ^[1][2]
• Department logo confusion. There is also a distinct endpoint for department-level logos (DELETE /api/v1/departments/{department_id}/logo), which operates on a different resource entirely. Don't mix up organization-level and department-level operations. ^[5]
• Insufficient OAuth scope. If your token was generated without Desk.settings.DELETE or Desk.settings.ALL, the API will return an authorization error. Re-generate your token with the correct scopes included. ^[7]
• Stale organization ID. Using an incorrect or outdated organization_id will result in a 404 or similar error. Always validate the ID against your current Zoho Desk environment before running destructive operations. ^[1]

What to check

• Scope coverage: Confirm your OAuth token includes Desk.settings.DELETE or Desk.settings.ALL before executing the call. ^[7]
• Correct resource path: Double-check that your request targets /favicon and not /logo or a department-level endpoint. ^[1][2][5]
• Post-deletion verification: Run a GET /api/v1/organizations/{organization_id}/favicon after deletion to confirm the resource has been removed successfully. ^[4]