bitlync Docs

Concepts

Store-served reads

Reads come from the synced store for that MSP tenant. One sync fills the store. Every ISV on that tenant reads the same copy.

Mechanism

The caller asks for tickets, devices, or other listed reads. Bitlync answers from the store. That path does not spend vendor budget. live=True is an opt-in live read when a store read is not enough.

What the caller sees

The response names the store and the last sync. Fields are served_from and last_synced_at.

store-served read
{
  "served_from": "store",
  "last_synced_at": "2026-07-11T14:03:22Z",
  "data": [{
    "status": "in_progress",
    "source": "psa",
    "raw": {}
  }]
}

Every canonical object includes vendor: { connector, native_id, native }. native is the same payload as .raw. .raw is read-only.