Skip to main content

API tokens and IDs

An API token lets your own software or an integration manage events in your account. The API is part of the Business plan. See Integrations and automation.

Create a token

  1. Select your name at the top right, then API Tokens.

  2. Under Create API Token, enter a Name that tells you where the token is used.

  3. Keep the permission event:all ticked. Creating events and collections needs it.

  4. Select Create.

  5. Copy the token straight away. It is shown only once.

Store the token like a password. Anyone who has it can manage your events.


​

Use the API

The base URL is https://my.calendarlink.com/api/v1. Send the token in every request as Authorization: Bearer <token>.


​

The full specification, with all endpoints, fields and examples, is at my.calendarlink.com/openapi.json (OpenAPI 3.1). You can import it into Postman, another API client or an AI agent.


​

A typical first run:

  1. GET /user returns your organizations. Use organizations[].id as the organization ID in all other requests.

  2. GET /{organization}/collection returns your collections. Use an id as collection_id.

  3. POST /{organization}/event creates an event. The response contains its public url.

Good to know

  • Dates: send start and end as local time and always include timezone, for example Europe/Amsterdam. Without it, the times are read as UTC. Responses return dates in UTC.

  • Rate limit: 60 requests per minute per user. Above that you get a 429 response; wait the number of seconds in the Retry-After header.

  • Errors: 401 means the token is missing, invalid or expired; 403 means the token or your role lacks permission; 422 lists the fields that are invalid.

Manage tokens

Manage API Tokens lists your tokens with their expiry date. A token is valid for 90 days; create a new one before it expires and update it where you use it.


​

To revoke a token, select Delete next to it and confirm. Software that still uses it stops working.


​

Find your IDs

  • Organization ID: Open Settings. The long code in the address bar after /organization/ is your organization ID. The API also returns it with GET /user.

  • Collection ID: Open the collection. The long code in the address bar after /collections/ is its ID.

  • Event ID: The API returns it as id when you create or list events. The short code at the end of the event page link, such as c42b9, does not work in the API.

Each collection has its own ID, different from the organization ID. Smart Links need the collection ID; see Smart Links.


​

For Zapier, Make, n8n and other ways to connect, see Integrations and automation.

Related Articles
Did this answer your question?