ChronSync
DevelopersReference

API scopes

A reference of every ChronSync API scope and the preset bundles — read-only, booking-agent, scheduler, full-access, and revdev-sync — you can grant an API key.

Each API key is granted a set of scopes that control exactly what it can read and write. When you create a key you can pick individual scopes or apply a preset bundle. A request that needs a scope the key doesn't hold is rejected.

Scopes

ScopeAllows
bookings:readRead bookings and their details.
bookings:writeCreate, update, cancel, and manage bookings.
event-types:writeCreate and update event types.
availability:readRead availability and open slots.
plans:readRead AI scheduling plans.
plans:writeCreate and update AI scheduling plans.
proposals:acceptAccept proposed times.
webhooks:writeCreate and manage webhook endpoints.
analytics:readRead booking and scheduling analytics.
users:provisionProvision and manage users.

Preset bundles

Bundles group the scopes that a common type of integration needs, so you don't have to assemble them by hand.

BundleIncludes
read-onlyAll the *:read scopes — read access with no writes.
booking-agentThe scopes needed to read availability and create and manage bookings.
schedulerThe scopes needed to drive AI scheduling — reading and writing plans and accepting proposals.
full-accessEvery scope.
revdev-syncThe scopes needed to keep ChronSync in sync with RevDev.

On this page