DELETE
/api/public/v1/tickets/{ticketId}Delete a ticket
Permanent. The ticket goes, and so do its checklist, comments, attachments, links, stated relations and activity trail — along with any builder session working on it. Deleting takes an item off every board and table it was being tracked on, so in the console it is a project manager’s call — everyone else moves work to Done.
Required scope
The access token must carry this scope. A token missing it gets 403 Forbidden. Grant them to an API client under Dev Tools → API, to an assistant or CLI sign-in when you approve or edit it under Dev Tools, and to a teammate under Employee → Permissions.
projects:admin
Path Parameters
| Name | Type | Required | Description |
|---|---|---|---|
ticketId | string | Required | Ticket ID. |
DELETEExample request
curl
curl -X DELETE "https://www.pxb.app/api/public/v1/tickets/{ticketId}" \
-H "Authorization: Bearer your_access_token"200Example response
json
{
"message": "Ticket deleted successfully!",
"content": {
"ticketId": "tkt_a1b2c3"
}
}403Example response
json
{
"message": "A ticket is deleted by a manager of its project, or by whoever filed it — and only while it is still New."
}In the console
The same thing done by hand, for anyone comparing the API against the screen they already use.