---
title: "Acknowledge transactions"
description: "Marks transactions as pulled by setting their `client_sync_status` to `synced`. If any id is wrong, nothing is updated and the response is `404`."
source: https://developers.qashio.com/v2/reference/post-public-v1-erp-transactions-acknowledge/
---

# Acknowledge transactions

`POST /public/v1/erp/transactions/acknowledge`

Requires a Bearer access token.

Marks 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. |

### Request body

```json
{
  "transaction_ids": [
    "c4943209-4462-455a-9bb9-f6781b3838bf"
  ]
}
```

### Example request

```bash
curl -X POST 'https://api.qashio.com/public/v1/erp/transactions/acknowledge' \
  -H 'Accept: application/json' \
  -H 'Authorization: Bearer <access_token>' \
  -H 'Content-Type: application/json' \
  -d '{
    "transaction_ids": [
      "c4943209-4462-455a-9bb9-f6781b3838bf"
    ]
  }'
```

### Example response (201)

```json
{
  "status_code": 201,
  "success": true,
  "data": {
    "message": "Status updated successfully.",
    "transaction_ids": [
      "c4943209-4462-455a-9bb9-f6781b3838bf"
    ]
  },
  "meta": {
    "request_id": "3adb2d16090c7b3bdbde3b326a814b30",
    "timestamp": "2026-09-09T10:07:52.143Z"
  }
}
```

### Errors

- `400` Bad Request - `transaction_ids` is empty, too long, or holds a value that is not a UUID
- `401` Unauthorized - missing or invalid Bearer token
- `404` Not Found - at least one id does not belong to this company, so nothing was updated
- `429` Too Many Requests - the endpoint accepts 2 requests per second