Skip to main content

Authorization

Follow this guide to create a new Cal.com credential that will allow Nexla to authenticate to and exchange data with your Cal.com account.
cal_com_api_auth.png

Cal.com

Prerequisites​

The Cal.com API v2 authenticates requests using an API key passed as a Bearer token in the Authorization header. Before creating the credential in Nexla, generate an API key from your Cal.com account.

Generate a Cal.com API Key​

  1. Sign in to your Cal.com account at app.cal.com.

  2. Click the drop-down menu next to your name in the lower-left corner of the dashboard, and select Settings.

  3. In the left-hand settings navigation, scroll to the Developer section, and click API keys.

  4. Click the + Add button in the upper-right corner of the API keys page to open the new key dialog.

  5. Enter a descriptive Personal note for the key (for example, Nexla integration) so the purpose of the key is clear later.

  6. Choose an expiration option for the key. Cal.com offers fixed durations (for example, 30 days, 90 days, 1 year) and a Never expires option. For production integrations, select an expiration that aligns with your organization's key-rotation policy.

  7. Click Save to generate the API key. Cal.com displays the new key on screen exactly once.

  8. Copy the generated API key and store it in a secure secret manager. Cal.com does not display the secret value again, and the key cannot be retrieved later.

    Cal.com API keys are prefixed with cal_ for keys issued in test mode and cal_live_ for keys issued in live mode. The key value carries the same privileges as your Cal.com login, so treat it as a secret.

For complete information about generating and managing API keys, see the Cal.com API v2 introduction and the Cal.com guide to API keys.

Rate Limits​

The Cal.com API enforces a default rate limit of 120 requests per minute per API key. Higher limits (for example, 200 requests per minute) can be requested through Cal.com support. Plan ingestion frequency and concurrency accordingly when configuring Nexla data flows that fan out across many Cal.com endpoints.

Important

The Cal.com API key grants full access to your Cal.com account, including the ability to create, modify, and cancel bookings. Store the key in a secure secret manager, never commit it to source control, and rotate it immediately if you suspect it has been exposed.

Create a Cal.com Credential​

  • To create a new Cal.com credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

Credential Name & Description​

  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Resource descriptions are recommended but are not required. They should be used to provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

Authentication Method​

  1. Enter the Cal.com API key that you generated in the prerequisites section in the API Key Value field. Nexla automatically sends this value to the Cal.com API in the Authorization: Bearer ${API_KEY} header on every request. This field is required and is stored securely as a secret.

    Paste the full API key value, including the cal_ or cal_live_ prefix. Do not include the word Bearer — Nexla adds the Bearer prefix automatically when constructing the Authorization header.

Save the Credential​

  1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential. Nexla validates the API key by issuing a test call to the Cal.com GET /v2/me endpoint before persisting the credential.

  2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.