Ticket API
Delete Ticket
Hard-delete a ticket and its associated messages plus workflow run history for data-retention purposes. Irreversible. Does not cascade to sub-tickets — callers must iterate them themselves.
DELETE
Delete Ticket
Authentication and permissions
Token requirements: Organization-scoped API key or Team-scoped API key. Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
Permissions joined by + are all required; or separates alternatives. Full-access keys still cannot call endpoints marked unsupported. Team keys must allow every team checked by the request. OAuth access depends on the user’s roles and resource access.
- Permanently delete: The team must enable hard-delete. A team manager cannot issue the tickets:admin permission; an organization admin can issue a restricted key with it.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The ID of the ticket to delete. The owning team is resolved server- side; callers do not (and must not) supply it.
Response
200 - application/json
Success
The response is of type DeleteTicketResponse · object.

