Deleting a "during actions" transition draft in Zoho Desk requires a single authenticated DELETE call to the transitions API, targeting the specific ticket and transition you want to remove.
Why this matters
Zoho Desk's blueprint feature lets you define actions that fire *during* a transition between states. When you're iterating on a blueprint design, you may create draft during-actions that need to be discarded before publishing. Knowing the correct API endpoint and required parameters lets you clean up stale drafts programmatically rather than hunting through the UI. This is especially useful when managing blueprints at scale or automating Desk configuration via scripts.
---
Step-by-step
Step 1. Gather your required identifiers.
Before making the call, you need two pieces of information: the ticketId of the ticket whose blueprint transition you're editing, and the transitionId that identifies the specific transition containing the during-actions draft you want to delete. Both are string values. [1]
Step 2. Construct the DELETE request.
Send an HTTP DELETE request to the following endpoint, substituting your real values for the path parameters:
DELETE /api/v1/tickets/{ticketId}/transitions/{transitionId}/duringActionsReplace {ticketId} with your ticket's ID and {transitionId} with the transition's ID. [1]
Step 3. Include any optional query parameters.
The endpoint also accepts an optional parameter p (passed as a query dict or body payload depending on your client). If you have no additional filtering needs, you can omit it or pass an empty object. [1]
Step 4. Execute the call in Python (optional helper).
If you're using a Python-based Zoho Desk API wrapper, the method signature looks like this:
def op_13_delete_during_actions_transition(self, ticketId: str, transitionId: str, p: dict = None):
return self.c.request("DELETE", f"/api/v1/tickets/{ticketId}/transitions/{transitionId}/duringActions", p, None)Call it by passing your ticketId and transitionId as strings. The p argument is optional and defaults to None. [1]
Step 5. Verify the response.
A successful deletion will return an HTTP 200 or 204 response with no error body. If the response contains an "error" key, the draft was not removed — check that both IDs are correct and that your OAuth token has the necessary Desk blueprint permissions. [1]
---
Common pitfalls
- Wrong IDs: Passing a
ticketIdthat doesn't match the ticket owning the transition will result in a 404 or permission error. Always confirm both IDs belong to the same ticket-transition pair before calling the endpoint. [1] - Stale OAuth tokens: The Zoho Desk API requires a valid OAuth 2.0 bearer token scoped to blueprint/transition management. An expired or under-scoped token will cause the DELETE to fail silently or return an auth error. [1]
- Deleting a non-draft: This operation targets a *draft* during-actions configuration. If the transition has already been published, the endpoint may not behave as expected — confirm the transition is still in draft state first. [1]
---
What to check
- Confirm the transition no longer has during-actions attached by fetching the transition record after deletion and verifying the during-actions list is empty or absent.
- Check your API credentials are scoped correctly for Zoho Desk blueprint operations, particularly if you receive a
401or403response. - Validate both path parameters (
ticketIdandtransitionId) are accurate string values pulled from your Zoho Desk environment before retrying. [1]
---
*Beam Help is an independent expert support resource for Zoho products and is not official Zoho support. Always test API changes in a sandbox or staging environment before applying them to production.*