da55306a5a
* --init * progress... * add more docs * bunch of changes and added back platform * development guides added * more guides in develop with cal * self hosted WIP * deployments * fix deployment steps * self-hosted guides * .. * Removed the development only sections * Removed 'with Cal.com' * use steps component for steps --------- Co-authored-by: Keith Williams <keithwillcode@gmail.com>
27 lines
972 B
Plaintext
27 lines
972 B
Plaintext
---
|
|
title: 'Introduction to API v2'
|
|
description: 'Introduction to Cal.com API v2 endpoints'
|
|
---
|
|
|
|
## Authentication
|
|
|
|
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 the Authorization header. For example, the request would go something like:
|
|
|
|
```
|
|
'Authorization': 'Bearer YOUR_API_KEY'
|
|
```
|
|
|
|
in your request header.
|
|
|
|
All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.
|