> For the complete documentation index, see [llms.txt](https://calcom.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://calcom.gitbook.io/docs/enterprise-features/api.md).

# API

The Cal.com API is a REST-styled API that gives control over almost the entire Cal.com platform by providing all the resources available to our customers, exposed as simple HTTP endpoints. \
Whether you need to create an event type, modify it, fetch it, or remove it from your account, you can do all that with simple API requests. This isn't restricted to event types alone. You can do it all with the other resources as well, such as, bookings, availabilities, integrated calendars, schedules, team memberships, payments and much more without ever need to use the UI.

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.

{% hint style="info" %}
We also provide an option for Admin API requests for some of our endpoints
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://calcom.gitbook.io/docs/enterprise-features/api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.