Acknowledge transactions
POST
/public/v1/erp/transactions/acknowledgeMarks transactions as pulled by setting their client_sync_status to synced. If any id is wrong, nothing
is updated and the response is 404.
| Value | Meaning |
|---|---|
not_synced | Not acknowledged yet. Every new transaction starts here. |
synced | Acknowledged with this endpoint. Your copy is current. |
outdated | Acknowledged, then changed. Pull it and acknowledge it again. |
Header parameters
company_idstringrequiredERP company UUID the transaction ids belong to.
Example
68c9f979-0360-4e4e-a5c5-327c8119ecb3
Request body
application/jsonrequired
| Field | Type | Description |
|---|---|---|
transaction_ids* | string<uuid>[] | ERP transaction UUIDs, taken from the id field of a transaction, not qashio_id. Between 1 and 200 ids; duplicates are removed before the update. |
Response
| Field | Type | Description |
|---|---|---|
status_code | integer | |
success | boolean | |
data | object | |
message | string | |
transaction_ids | string<uuid>[] | The de-duplicated list of ids that were marked as acknowledged. |
meta | object | |
request_id | string | |
timestamp | string |
Errors
400Bad Request -transaction_idsis empty, too long, or holds a value that is not a UUID401Unauthorized - missing or invalid Bearer token404Not Found - at least one id does not belong to this company, so nothing was updated429Too Many Requests - the endpoint accepts 2 requests per second
Every error carries an errors[] array and a meta.request_id. See Errors for the full envelope.