The sync model

Most write operations in Sync2Books are asynchronous. When you submit data — an expense, a bill, an invoice — Sync2Books accepts it, returns a syncBatchId immediately, and pushes it to the external system in the background. You confirm the outcome by reading the batch or the entity back. The same batch/status vocabulary applies to every write in the Accounting API. (The eTIMS API works differently: a sale is answered with its KRA result directly. See eTIMS core concepts.)

The flow

You submit            POST /expenses/{connectionId}      ─▶  { syncBatchId }
Sync2Books pushes     (background) ──▶ QuickBooks / Xero / Sage / …
You confirm           GET /sync/batches/{syncBatchId}    ─▶  status + per-item results

A sync batch groups one or more items. Each item tracks the fate of a single entity (one expense, one sale) and carries the external system’s response once done.

Statuses

Batch / item status	Meaning
`pending`	Accepted, not yet pushed.
`syncing`	Currently being pushed to the external system.
`synced` / `success`	Accepted by the external system; response stored.
`failed`	Rejected; `syncError` explains why.
`skipped`	Intentionally not synced (e.g. duplicate or filtered).

Confirm a result

curl -X GET "https://api.sync2books.com/sync/batches/{syncBatchId}" \
  -H "X-API-Key: {apiKey}"

{
  "batch": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "status": "completed",
    "totalItems": 1,
    "successfulItems": 1,
    "failedItems": 0
  },
  "items": [
    {
      "entityId": "expense-001",
      "entityType": "Expense",
      "status": "success",
      "integrationResponse": { "id": "qb-expense-id", "syncToken": "0" },
      "syncErrorMessage": null
    }
  ]
}

Rather than polling, you can subscribe to webhooks to be notified when a batch completes. Inbound webhooks are verified with your whsec_… webhook secret — see Authentication.

Product-specific result tracking

Expenses — see Sync transactions for status handling and error recovery.
eTIMS — a separate product with its own model: a sale is submitted and answered with the signed KRA receipt in one request. See eTIMS core concepts.

Get started

Core concepts

Accounting API — Expenses

Accounting API — Connected systems

Link component

The flow

Statuses

Confirm a result

Product-specific result tracking

Next steps

Environments & base URLs

Errors & rate limits

​The flow

​Statuses

​Confirm a result

​Product-specific result tracking

​Next steps

Environments & base URLs

Errors & rate limits

The flow

Statuses

Confirm a result

Product-specific result tracking

Next steps