Delete transaction: not available
Transactions cannot be deleted. Every transaction you send stays on record: it is the basis of the solutions you subscribe to and of your company’s history. The endpoint still exists, but it always refuses the request.
Endpoint
Section titled “Endpoint”DELETE
https://api.rapidchargeback.com/api/v1/transactions/:idAuthentication
Section titled “Authentication”Authorization: Basic base64(client_id:client_secret)What the API responds
Section titled “What the API responds”| Situation | HTTP | Code |
|---|---|---|
| Transaction exists and belongs to your company | 405 | TRANSACTION_DELETE_NOT_ALLOWED |
| Transaction does not exist or belongs to another company | 404 | TRANSACTION_NOT_FOUND |
Neither response deletes anything. Do not retry: the response will be the same.
What to do instead of deleting
Section titled “What to do instead of deleting”- Wrong data in a transaction not used yet: fix it with Update transaction (
PATCH /api/v1/transactions/:id). - Transaction already used by a solution (e.g. queried by Prevention): it can no longer be changed.
PATCHresponds409 TRANSACTION_IMMUTABLE. See Immutability protection. - Integration that called DELETE: remove the call. It no longer has any effect.
Request example
Section titled “Request example”curl -X DELETE https://api.rapidchargeback.com/api/v1/transactions/00000000-0000-0000-0000-000000000042 \ -H "Authorization: Basic Y2xpZW50X2lkOmNsaWVudF9zZWNyZXQ="Response examples
Section titled “Response examples”Deletion not allowed
Section titled “Deletion not allowed”HTTP/1.1 405 Method Not Allowed{ "error": { "code": "TRANSACTION_DELETE_NOT_ALLOWED", "message": "Transactions cannot be deleted" }}Transaction not found
Section titled “Transaction not found”HTTP/1.1 404 Not Found{ "error": { "code": "TRANSACTION_NOT_FOUND", "message": "Transaction not found" }}