Cal.com API v2

This skill provides guidance for AI agents to interact with the Cal.com API v2, enabling scheduling automation, booking management, and calendar integrations.

Base URL

All API requests should be made to:
CODEBLOCK0

Authentication

All API requests require authentication via Bearer token in the Authorization header:

CODEBLOCK1

API keys must be prefixed with cal_. You can generate API keys from your Cal.com dashboard under Settings > Developer > API Keys.

Core Concepts

Event Types

Event types define bookable meeting configurations (duration, location, availability rules). Each event type has a unique slug used in booking URLs.

Bookings

Bookings are confirmed appointments created when someone books an event type. Each booking has a unique UID for identification.

Schedules

Schedules define when a user is available for bookings. Users can have multiple schedules with different working hours.

Slots

Slots represent available time windows that can be booked based on event type configuration and user availability.

Common Operations

Check Available Slots

Before creating a booking, check available time slots:

CODEBLOCK2

Query parameters:

• - startTime (required): ISO 8601 start of range
• INLINECODE2 (required): ISO 8601 end of range
• INLINECODE3 or eventTypeSlug: Identify the event type
• INLINECODE5: Timezone for slot display (default: UTC)

Response contains available slots grouped by date.

Create a Booking

CODEBLOCK3

Required fields:

• - start: ISO 8601 booking start time
• INLINECODE7: ID of the event type to book
• INLINECODE8: Attendee's full name
• INLINECODE9: Attendee's email address
• INLINECODE10: Attendee's timezone

Get Bookings

List bookings with optional filters:

CODEBLOCK4

Query parameters:

• - status: Filter by status (upcoming, recurring, past, cancelled, unconfirmed)
• INLINECODE12: Filter by attendee email
• INLINECODE13: Filter by event type
• INLINECODE14: Number of results (max 250)
• INLINECODE15: Pagination offset

Get a Single Booking

CODEBLOCK5

Cancel a Booking

CODEBLOCK6

Reschedule a Booking

CODEBLOCK7

List Event Types

CODEBLOCK8

Returns all event types for the authenticated user.

Get a Single Event Type

CODEBLOCK9

Create an Event Type

CODEBLOCK10

List Schedules

CODEBLOCK11

Get Default Schedule

CODEBLOCK12

Create a Schedule

CODEBLOCK13

Days are 0-indexed (0 = Sunday, 1 = Monday, etc.).

Get Current User

CODEBLOCK14

Returns the authenticated user's profile information.

Team and Organization Endpoints

For team bookings and organization management, use the organization-scoped endpoints:

List Organization Teams

CODEBLOCK15

Get Team Event Types

CODEBLOCK16

Create Team Booking

Team event types support different scheduling modes:

• - COLLECTIVE: All team members must attend
• INLINECODE17: Distributes bookings among team members

Webhooks

Configure webhooks to receive real-time notifications:

List Webhooks

CODEBLOCK17

Create a Webhook

CODEBLOCK18

Available triggers:

• - INLINECODE18
• INLINECODE19
• INLINECODE20
• INLINECODE21
• INLINECODE22
• INLINECODE23

Calendar Integration

List Connected Calendars

CODEBLOCK19

Check Busy Times

CODEBLOCK20

Error Handling

The API returns standard HTTP status codes:

• - 200: Success
• INLINECODE25: Created
• INLINECODE26: Bad Request (invalid parameters)
• INLINECODE27: Unauthorized (invalid or missing API key)
• INLINECODE28: Forbidden (insufficient permissions)
• INLINECODE29: Not Found
• INLINECODE30: Unprocessable Entity (validation error)
• INLINECODE31: Internal Server Error

Error responses include a message field:

CODEBLOCK21

Rate Limiting

The API implements rate limiting. If you exceed the limit, you'll receive a 429 Too Many Requests response. Implement exponential backoff for retries.

Pagination

List endpoints support pagination via take and skip parameters:

• - take: Number of items to return (default: 10, max: 250)
• INLINECODE36: Number of items to skip

Best Practices

1. 1. Always check slot availability before creating bookings
2. Store booking UIDs for future reference (cancel, reschedule)
3. Handle timezone conversions carefully - always use ISO 8601 format
4. Implement webhook handlers for real-time booking updates
5. Cache event type data to reduce API calls
6. Use appropriate error handling for all API calls

Additional Resources

• - Full API Reference
• OpenAPI Specification