9d39742802
* Update docs/api-reference/v1/introduction.mdx * Update docs/api-reference/v1/authentication.mdx * Update docs/api-reference/v1/errors.mdx * Update docs/api-reference/v1/rate-limit.mdx * Update docs/mint.json --------- Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
22 lines
1.0 KiB
Plaintext
22 lines
1.0 KiB
Plaintext
---
|
|
title: "Authentication"
|
|
---
|
|
|
|
<Warning>
|
|
**API v1 is deprecated and will be discontinued on February 15, 2026.** Please migrate to [API v2](/api-reference/v2/introduction) as soon as possible.
|
|
</Warning>
|
|
|
|
The Cal.com API uses API keys to authenticate requests. You can view and manage your API keys in your settings page under the security tab in Cal.com.
|
|
|
|
<img src="/images/i1600x899-DllqhV6w_3Vj_oxtjov.png" />
|
|
|
|
API Keys are under Settings > Security
|
|
|
|
Test mode secret keys have the prefix `cal_` and live mode secret keys have the prefix `cal_live_`.
|
|
|
|
Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth.
|
|
|
|
Authentication to the API is performed via URL Query Params. Provide your API key as a query param like: `https://api.cal.com/v1/?apiKey=cal_live_xxxxxx`
|
|
|
|
All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.
|