Welcome to the developer docs, the more advanced documentation covering how to build on top of Cal.com both in the codebase, by API and more. These guides will go into depth on how you can best integrate and extend Cal.com for your needs.
Most of this documentation relates to the Cal.com API, but is also the home for handy guides walking you through certain tasks like adding CSS, or outlining the structure for building apps.
The Cal.com API is a REST-styled API that gives full control over the entire Cal.com platform by providing all the resources available to our customers, exposed as simple HTTP endpoints.
The Cal.com API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.
You can use the Cal.com API in our test environment at https://cal.dev, which doesn't affect your live data or interact with your real calendar connected apps.
The API key you use to authenticate the request determines whether the request is live mode or test mode.
You'll also need to make your calls to either of those endpoints depending on your environment:
The API supports HTTP versions 1, 1.1, and 2, although HTTP/2 is preferred.
TLS versions 1.2 and 1.3 are supported, with resumption.
All requests must be encoded as JSON with the Content-Type: application/json header. If not otherwise specified, responses from the Cal.com API, including errors, are encoded exclusively as JSON as well.
Want to jump right in?
Feeling like an eager beaver? Jump in to the quick start docs and get making your first request: