DELETE
/api/public/v1/transactions/{transactionId}Void a transaction
The ledger is append-only in spirit: this moves the row to VOIDED and reverses its journal entry rather than removing the record. Its receipt is dropped from storage at the same time, because a voided transaction never shows one again and the company would otherwise keep paying to store a file it cannot reach. Needs `transactions:admin` — it is the ledger’s one irreversible act.
Required scope
The access token must carry this scope. A token missing it gets 403 Forbidden. Grant them to an API client under Settings → Company → API, and to a teammate under Employee → Permissions.
transactions:admin
Path Parameters
| Name | Type | Required | Description |
|---|---|---|---|
transactionId | string | Required | Transaction ID. |
DELETEExample request
curl
curl -X DELETE "https://www.pxb.app/api/public/v1/transactions/{transactionId}" \
-H "Authorization: Bearer your_access_token"200Example response
json
{
"message": "Transaction voided!",
"content": {
"transaction": {
"id": "txn_4410",
"type": "EXPENSE",
"status": "VOIDED",
"amount": -48000,
"description": "Q3 hosting",
"counterpartyName": "Cloud Co",
"irsCategory": "Utilities",
"date": "2026-08-01T00:00:00.000Z",
"dueDate": "2026-09-01T00:00:00.000Z",
"legalEntityId": "le_7788",
"createdAt": "2026-08-01T09:00:00.000Z",
"updatedAt": "2026-08-01T09:00:00.000Z"
}
}
}In the console
The same thing done by hand, for anyone comparing the API against the screen they already use.