Skip to main content
The Cal ID API key is a secure credential that connects your scheduling data with external applications, custom websites, or the API docs. It lets different software systems communicate with your Cal ID account safely.

Create your API key

1

Open the developer dashboard

Log in to your Cal ID account, click Settings, then scroll the left sidebar to the Developer section and click API Keys.
API Keys page under Settings → Developer, listing existing keys beside a Create an API Key button

Finding where your keys are managed

2

Start a new key

Click Create an API Key in the top-right corner of the API Keys page. A configuration window appears.
3

Name the key

Enter a descriptive name in the Name this key field — for example, “My Personal Portfolio” or “Zapier Integration.” A clear name helps you identify later which app uses which key.
4

Set an expiration

Decide how long the key stays active.
Switch the Never expires toggle ON. The key stays active until you manually delete it.
5

Create and copy the key

Click Create. Your secret key is shown once — click the copy icon and paste it somewhere safe, like a password manager.
For your protection, Cal ID will never show this key again. If you close the window without copying it, delete the entry and create a new one.

Make your first request

Send an authenticated request to the me endpoint to confirm your key works — it returns your profile details.
Here’s the same call with curl:
Replace calid_XXXXXX with your API key.
Prefer to explore interactively? Open the API Reference, click Authorize, paste your key, and run any endpoint against your live account right from the docs.

Key security rules

  • Never share your API key in emails, chat messages, or public code repositories like GitHub.
  • Use separate keys for different integrations — safer than reusing one key everywhere.
  • Revoke unused keys from the API Keys page with the Delete (trash) icon to cut off access instantly.

Watch your call volume

Every response returned for your key carries X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers, and Cal ID answers with 429 Too Many Requests once you run out of allowance. Read API rate limits for the retry and back-off pattern to build in from the start — and note that using a separate key per integration makes it far easier to spot which one is being noisy.

Start using your key

Explore the API Reference

Authorize once, then try every endpoint against your live account.

Create your first booking

A step-by-step recipe for booking through the API.

API rate limits

Read the rate-limit headers and back off cleanly from a 429.