Sync

Client SDK uses these endpoints for background delta sync. Conflicts are resolved server-wins — if the server has a newer last_synced_at than the incoming change's client_timestamp, the client gets a conflict record and keeps the server value.

Source: apps/api/src/routes/client/sync.ts.

Endpoints

Method	Path	Description
POST	`/client/sync`	Push local changes.
GET	`/client/sync`	Pull remote changes since a checkpoint.

POST /client/sync

Request (`SyncPushInput`)

{
  "changes": [
    {
      "entity_type": "todo",
      "entity_id": "…",
      "action": "update",
      "data": { "title": "…" },
      "client_timestamp": "…"
    }
  ]
}

Response 200

{
  "data": {
    "applied": 1,
    "conflicts": [
      {
        "entity_type": "todo",
        "entity_id": "…",
        "resolution": "server_wins",
        "server_data": { "last_synced_at": "…" }
      }
    ],
    "checkpoint_token": "…"
  }
}

Errors

500 SYNC_FAILED.

Try it:

POST/client/sync

client auth

curl -X POST 'https://api.amba.dev/client/sync'

Loading auth… Configure auth in the settings drawer (top-right) to run this request.

Curl:

curl -X POST '${BASE_URL}/client/sync' \
  -H 'X-Api-Key: ${CLIENT_API_KEY}' \
  -H 'Authorization: Bearer ${SESSION_TOKEN}' \
  -H 'Content-Type: application/json' \
  -d '{}'

GET /client/sync

Pull up to 100 changes newer than the supplied checkpoint.

Query

Param	Required	Description
`entity_type`	yes	The entity kind to sync (must be a simple identifier; LIKE metacharacters are escaped).
`checkpoint_token`	no	Opaque token from a prior response. Omitting = full sync from epoch.