Create an API key
Generate a scoped API key in ChronSync and use it as a Bearer token to authenticate requests to the REST API.
Generate a key that lets your integration authenticate to the ChronSync API. Each key carries a set of scopes that control exactly what it can read and write.
Before you start
- You need access to Settings for your account.
- Decide which scopes your integration needs. See API scopes.
Create the key
Go to Settings → API Keys.
[Screenshot: The API Keys page under Settings, listing existing keys]
Click to create a new key and give it a name that describes its use — for example, Website embed or RevDev sync.
Choose its scopes. Pick a preset bundle — read-only, booking-agent, scheduler, full-access, or revdev-sync — or select individual scopes for finer control.
[Screenshot: The scope selector showing preset bundles and individual scope checkboxes]
Optionally set an expiry in days. Leave it unset for a key that doesn't expire.
Create the key, then copy the full key value and store it somewhere secure.
The full key is shown only once, right after you create it. Copy it and store it securely — if you lose it, you'll need to create a new one. Never commit a key to source control or expose it in client-side code.
The new key appears in the list on the API Keys page. It's ready to use immediately.
Use the key
Send the key as a Bearer token in the Authorization header on every request:
Authorization: Bearer cs_live_your_api_key_hereRevoke a key
You can revoke a key at any time from the API Keys page. Revoking takes effect immediately and any request using that key will start failing — rotate to a new key before you revoke an old one.
Related
Developers
Build on ChronSync with API keys, the REST API, webhooks, and an embeddable booking widget — everything you need to integrate scheduling into your own app.
Set up webhooks
Register a webhook endpoint in ChronSync to receive signed HTTP POST notifications when bookings, plans, payments, and waitlist entries change.