How to delete spam calls in Zoho Desk

Deleting spam calls in Zoho Desk is straightforward once you know the right endpoint — a single API call removes all flagged spam call records from your portal.

Why this matters

Spam calls can clutter your Zoho Desk call logs, making it harder for agents to focus on genuine customer interactions. If your team uses Zoho Desk's telephony features, spam entries accumulate over time and can slow down reporting and queue management. Knowing how to programmatically purge these records keeps your call data clean and your agents productive.

> Note: Beam Help is an independent expert support resource — not official Zoho support.

---

Step-by-step

Step 1. Confirm you have API access to your Zoho Desk portal and that your integration credentials (OAuth token or API key) are ready. You will need permission to perform DELETE operations against the Zoho Desk calls resource before proceeding.

Step 2. Construct your request targeting the spam calls endpoint. The operation is a DELETE request sent to /api/v1/calls/spam on your Zoho Desk instance. This endpoint is specifically designed to remove spam call entries in bulk. ^[8]

Step 3. Pass any required query or body parameters using the p dictionary argument if your integration layer supports it. The endpoint accepts an optional parameters object (p) alongside the DELETE method, so you can scope the deletion if needed. ^[8]

Step 4. Execute the request. Using Python as an example, the call looks like this:

def delete_spam_calls(self, p: dict = None):
    """Delete Spam Calls"""
    return self.c.request("DELETE", f"/api/v1/calls/spam", p, None)

Send the DELETE request to /api/v1/calls/spam, passing your parameters object as the body or query string depending on your client library. ^[8]

Step 5. Check the HTTP response code returned by Zoho Desk. A successful deletion will return a 2xx status, confirming that the spam call records have been removed from your portal. If you receive an error code, review your authentication headers and parameter formatting before retrying.

---

Common pitfalls

• Missing or expired credentials. The DELETE operation will fail silently or return a 401/403 if your OAuth token has expired or lacks the necessary scope. Refresh your token and confirm it has write/delete permissions for the calls resource before running the request. ^[8]

• No native UI option for bulk spam call deletion. Based on what our team has reviewed, there is currently no built-in button inside the Zoho Desk interface to bulk-delete spam calls — the API route at /api/v1/calls/spam is the supported path for this action. ^[8]

• Confusing Zoho Desk calls with Zoho Mail spam. The /api/v1/calls/spam endpoint is specific to telephony call records inside Zoho Desk and is entirely separate from Zoho Mail's anti-spam or email deletion APIs, which use different endpoints and OAuth scopes. ^[3][6] Make sure you are targeting the correct product and endpoint.

---

What to check

• Verify the endpoint URL — confirm you are sending the DELETE request to /api/v1/calls/spam and not a mail or analytics endpoint. ^[8]
• Confirm the response status — a 2xx response indicates successful deletion; log any error codes for troubleshooting.
• Review your call logs after deletion — navigate to the Calls section in Zoho Desk to confirm that spam entries no longer appear in your queue or reports.