Tenmark Sync
Sync API · v2

Keep field devices and back-office records in agreement.

Tenmark Sync moves incremental changes between handheld terminals, warehouse scanners and your central database. Offline-first, conflict-aware, and quiet when nothing has changed.

Read the docsService status
Delta

Incremental by default

Clients send a cursor, receive only what changed since. Typical payloads stay under a few kilobytes.

Offline

Works through gaps

Devices queue writes locally and replay them in order when the link returns. No manual resync.

Merge

Predictable conflicts

Field-level last-writer rules or custom resolvers. Every merge is recorded and can be audited.

One endpoint, one cursor

The sync endpoint accepts a batch of local changes and returns the remote changes the device has not seen yet. Authentication uses per-device tokens issued by your administrator.

Endpoints are not browsable. Requests without a valid device token are rejected.

# pull and push in a single round trip
POST /api/v2/sync
Authorization: Device <token>

{
  "cursor": "c_8f21a0",
  "changes": [
    { "table": "stock", "id": 4412, "qty": 18 }
  ]
}

Service status

Sync APIOperational
Device token serviceOperational
Admin consoleOperational