How to delete validation rules in Zoho Desk

Deleting a validation rule in Zoho Desk is done through a single authenticated API call that targets a specific layout and rule by their respective IDs. Here at Beam Help — independent expert support for Zoho, not official Zoho support — we walk you through exactly what's needed.

Why this matters

Validation rules control what data agents and customers can submit on ticket forms. Over time, rules become outdated, conflict with new workflows, or simply need to be retired. Knowing how to remove them cleanly via the API is essential for teams managing Zoho Desk programmatically or through automation pipelines.

Step-by-step

Step 1. Gather your credentials and OAuth scopes.

Before making any API call, confirm your OAuth token includes the correct Zoho Desk permissions. The scopes you need for settings-level operations — including deleting validation rules — fall under the Desk.settings.ALL or Desk.settings.DELETE scope groups. Make sure your connected app has at least one of these scopes authorised. ^[2]

Step 2. Identify your layoutId and validationRuleId.

The delete endpoint requires two path parameters: the ID of the layout the rule belongs to (layoutId) and the unique identifier of the rule itself (validationRuleId). You can retrieve these by first calling the relevant list or get endpoints for layouts and their associated validation rules in Zoho Desk. Keep both values handy before proceeding.

Step 3. Send the DELETE request.

Issue an HTTP DELETE request to the following endpoint, substituting your actual IDs:

DELETE /api/v1/layouts/{layoutId}/validationRules/{validationRuleId}

For example, using the Python client wrapper, the call looks like this: ^[1]

result = desk_api.delete_validation_rule(
    layoutId="your_layout_id",
    validationRuleId="your_rule_id"
)

The method sends a DELETE request to /api/v1/layouts/{layoutId}/validationRules/{validationRuleId} and returns the API response. ^[1]

Step 4. Handle the response.

A successful deletion will return a confirmation from Zoho Desk. If the response contains an error key, inspect the message carefully. Common causes include an invalid or mismatched layoutId/validationRuleId, or an expired/insufficient OAuth token. ^[3]

Step 5. Re-authenticate if you receive a 401 status.

If the API returns an HTTP 401, your access token has either expired or lacks the required scopes. Reconnect your Zoho integration and ensure the Desk.settings.DELETE scope is included before retrying. ^[3]

Common pitfalls

• Wrong scope: Using only Desk.tickets.ALL or Desk.basic.READ is not sufficient. Settings-level operations require Desk.settings.ALL or the more specific Desk.settings.DELETE scope. Double-check your scope configuration. ^[2]
• Mismatched IDs: Passing a validationRuleId that does not belong to the specified layoutId will cause the request to fail. Always verify the rule is actually associated with the layout you're targeting before calling the endpoint. ^[1]
• Token expiry: If your access token has passed its expiry time, the API will reject the request with a 401 error. Implement a token-refresh step before making destructive calls to avoid this. ^[3]
• High-risk confirmation: When using automated plan-execution tooling, destructive operations may trigger an additional confirmation prompt before the call is dispatched. Ensure your automation flow accounts for this gate. ^[6]

What to check

• Confirm the rule is gone: After deletion, call the list endpoint for validation rules on the same layout and verify the rule ID no longer appears in the results.
• Scope coverage: Review your OAuth configuration and confirm Desk.settings.DELETE (or Desk.settings.ALL) is present and active for the connected account. ^[2]
• No dependent rules: Check whether any other layout configurations or automation rules referenced the deleted validation rule, and update them accordingly to avoid silent failures.