Skip to main content
DELETE
/
receipts
/
{id}
Delete receipt
curl --request DELETE \
  --url https://integrations.clopos.com/open-api/receipts/{id} \
  --header 'x-brand: <api-key>' \
  --header 'x-token: <api-key>' \
  --header 'x-venue: <api-key>'
{
  "success": true,
  "message": "<string>",
  "time": 123,
  "timestamp": "<string>",
  "unix": 123
}

​
Purpose

Delete a receipt that was created in error before it is reconciled in downstream reports.

​
HTTP Request

DELETE https://integrations.clopos.com/open-api/receipts/{id}

​
Path Parameters

ParameterTypeDescription
idnumberIdentifier of the receipt to delete.

​
Request Example

curl --location --request DELETE "https://integrations.clopos.com/open-api/receipts/16" \
  -H "x-token: oauth_example_token" \
  -H "x-brand: openapitest" \
  -H "x-venue": "1"

​
Response

​
200 OK — Receipt deleted

{
  "success": true,
  "message": "Receipt removed successfully",
  "time": 112,
  "timestamp": "2025-10-06 09:30:15",
  "unix": 1759743015
}

​
404 Not Found — Invalid ID

{
  "success": false,
  "error": "not_found",
  "message": "Receipt not found"
}

​
Notes

  • Deleting a receipt is irreversible; ensure it is not already part of financial exports before removing it.
  • Any associated stock operations are rolled back; confirm with your back-office team before deleting live data.
  • To maintain audit trails, consider storing the deletion response in your logs.

Authorizations

​
x-token
string
header
required

Access token obtained from /auth endpoint

​
x-brand
string
header
required

Brand identifier

​
x-venue
string
header
required

Venue identifier

Path Parameters

​
id
integer
required

Receipt ID

Response

Receipt deleted successfully

​
success
boolean
​
message
string
​
time
integer
​
timestamp
string
​
unix
integer