For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Contact Us
Knowledge BaseProduct UpdatesAPI Documentation
Knowledge BaseProduct UpdatesAPI Documentation
    • Getting Started
  • API Reference
      • GETCheck if a transaction exists
      • POSTAdd a new transaction
      • PUTUpdate an existing transaction
      • DELSubmit a deletion request for a transaction and any related data
      • POSTAdd transactions in batch
      • PUTUpdate transactions in batch
Contact Us
LogoLogo
API ReferenceTransactions

Submit a deletion request for a transaction and any related data

DELETE
https://api.cable.tech/v2/transaction
DELETE
/v2/transaction
$curl -X DELETE https://api.cable.tech/v2/transaction \
> -H "Authorization: Bearer <token>" \
> -H "Content-Type: application/json" \
> -d '{
> "tx_id": "a3f1c9e2-7b4d-4f8a-9d2e-5b6c7d8e9f01",
> "reason": "Duplicate transaction entry detected"
>}'
1{
2 "tx_id": "a3f1c9e2-7b4d-4f8a-9d2e-5b6c7d8e9f01",
3 "deletion_request_id": "d4e5f6a7-b8c9-40d1-9e2f-3a4b5c6d7e8f"
4}
This operation will submit a request to delete the transaction and any related data. The deletion request will be processed by the system and the data will be removed permanently from Cable's system. Deletion requests are not processed immediately and may take some time to complete. The status of the deletion request can be checked using the deletion request ID and the status endpoint. <Warning>This operation is not intended for regular use and should be used with caution.</Warning>
Was this page helpful?
Previous

Add transactions in batch

Next
Built with

This operation will submit a request to delete the transaction and any related data.

The deletion request will be processed by the system and the data will be removed permanently from Cable’s system. Deletion requests are not processed immediately and may take some time to complete.

The status of the deletion request can be checked using the deletion request ID and the status endpoint.

This operation is not intended for regular use and should be used with caution.

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Request

This endpoint expects an object.
tx_idstringRequired
The unique identifier of the transaction
reasonstringRequired
The reason for deletion

Response

Deletion request submitted successfully
tx_idstring
The unique identifier of the transaction
deletion_request_idstring
The unique identifier of the deletion request

Errors

401
Unauthorized Error
404
Not Found Error
429
Too Many Requests Error
500
Internal Server Error