canonical: https://jentic.com/apis/calendly.com/calendly # Calendly API Jentic publishes the only available OpenAPI specification for Calendly API, keeping it validated and agent-ready. Schedule meetings, manage event types, and track invitee responses across 25 endpoints. Supports organization management, webhook subscriptions for booking notifications, routing forms for intelligent scheduling, and GDPR-compliant invitee data deletion. ## For AI agents Schedule meetings, list event types, and retrieve invitee details for automated calendar workflows. Supports webhook subscriptions and routing form submissions across 25 endpoints. ## Scope Does not handle video conferencing, calendar sync, or payment collection - use for scheduling link generation and event tracking only. ## Capabilities - Schedule one-on-one and group meetings by generating shareable scheduling links - Query scheduled events filtered by date range, status, and invitee email - Subscribe to webhook notifications for event creation, cancellation, and invitee responses - Route scheduling requests through configurable forms with conditional logic - Retrieve organization membership and manage team member invitations - Cancel scheduled events with reason tracking and invitee notification - Delete invitee personal data for GDPR and privacy compliance requests ## Use cases ### AI Agent Meeting Scheduling AI agents use the Calendly API through Jentic to automate meeting scheduling without requiring users to manually share calendar links. An agent searches for the scheduling operation, loads the schema, and generates a one-time scheduling link programmatically. This enables chatbots, sales assistants, and support agents to book meetings in real time during conversations. Example prompt: Create a scheduling link for event type UUID 'abc-123' with max_event_count set to 1 and return the booking URL ### Sales Pipeline Event Tracking Track prospect meeting activity by querying scheduled events filtered by invitee email or date range. The Calendly API returns event details including start time, duration, location, and cancellation status. Sales teams integrate this data into CRM pipelines to measure meeting-to-close rates and identify prospects who no-show or reschedule frequently. Example prompt: List all scheduled events between 2026-04-01 and 2026-04-30 for invitee email 'prospect@company.com' and return event status and start times ### Webhook-Driven Booking Notifications Subscribe to Calendly webhooks to receive real-time notifications when meetings are created, canceled, or rescheduled. Each webhook payload includes the event URI, invitee details, and scheduling metadata. This eliminates polling and enables instant downstream actions like sending confirmation emails, updating CRM records, or triggering onboarding workflows. Example prompt: Create a webhook subscription for organization UUID 'org-456' listening to 'invitee.created' events with callback URL 'https://hooks.example.com/calendly' ### Lead Routing with Scheduling Forms Use Calendly routing forms to qualify leads before they book a meeting. The API exposes routing form configurations and submission data, allowing agents to analyze which routing paths prospects take and which team members they are assigned to. This data feeds lead scoring models and ensures high-value prospects reach the right sales rep. Example prompt: Retrieve all submissions for routing form UUID 'form-789' and return the selected routing path and assigned event type for each ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /api/v2/scheduling_links | Generate a scheduling link | | GET | /api/v2/scheduled_events | List scheduled events | | GET | /api/v2/scheduled_events/{uuid}/invitees | List invitees for an event | | POST | /api/v2/scheduled_events/{uuid}/cancellation | Cancel a scheduled event | | POST | /api/v2/webhook_subscriptions | Create a webhook subscription | | GET | /api/v2/event_types | List event types | | GET | /api/v2/routing_forms/{uuid}/submissions | List routing form submissions | ## Key resources - **Scheduled Events** — Query, filter, and cancel meetings with invitee details and status tracking - **Event Types** — List and inspect available meeting types with duration, location, and scheduling rules - **Webhook Subscriptions** — Subscribe to real-time notifications for booking lifecycle events - **Routing Forms** — Inspect form configurations and retrieve submission responses for lead routing - **Organizations** — Manage team memberships, invitations, and organizational settings ## Why Jentic - **Setup:** Wiring the Calendly API by hand means managing bearer tokens, refreshing OAuth credentials, and stitching together scheduling links, scheduled events, and webhook subscriptions yourself. Through Jentic you install once, import Calendly from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Calendly puts the event uuid in the URL path (/scheduled_events/{uuid}/...), so a rule can pin your agent to one scheduled event: it can read that event's invitees and nothing else. You choose the operations it may call, so actions like /scheduled_events/{uuid}/cancellation or creating webhook subscriptions are not included unless you add them. - **Credential handling:** Your Calendly bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a scheduling link' or 'list scheduled events', and Jentic returns the matching Calendly operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Zoom Meetings API** — Zoom provides the video conferencing infrastructure that Calendly events often connect to - **HubSpot Meetings** — HubSpot offers built-in meeting scheduling tied directly to its CRM contact records - **Slack Web API** — Slack enables meeting booking notifications and reminders in team channels ## FAQ ### Why is there no official OpenAPI spec for Calendly API? Calendly does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Calendly API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Calendly API use? The Calendly API uses Bearer token authentication. You include a Personal Access Token or OAuth 2.0 access token in the Authorization header as 'Bearer {token}'. Through Jentic, tokens are stored encrypted in your Jentic One instance and agents receive scoped credentials without handling raw tokens. ### Can I create scheduling links programmatically with the Calendly API? Yes. POST /api/v2/scheduling_links accepts an owner URI (your user or event type) and max_event_count parameter. It returns a unique booking URL that you can share with invitees. Set max_event_count to 1 for single-use links or omit it for reusable ones. ### What are the rate limits for the Calendly API? Calendly enforces rate limits per OAuth token. The standard limit is 180 requests per minute for most endpoints. Responses include rate limit headers (X-RateLimit-Limit, X-RateLimit-Remaining) so you can throttle requests before hitting the cap. ### How do I list upcoming scheduled events through Jentic? Search Jentic for 'list scheduled Calendly events'. Jentic returns the GET /api/v2/scheduled_events operation with its query parameters (min_start_time, max_start_time, status, invitee_email). Load the schema, set your date range and filters, then execute to get paginated event results. ### Does the Calendly API support webhooks for booking notifications? Yes. POST /api/v2/webhook_subscriptions creates a subscription for events like invitee.created, invitee.canceled, and routing_form_submission.created. You specify a callback URL, organization URI, scope, and event types. Calendly sends POST payloads to your URL within seconds of each event. ### Can I delete invitee data for GDPR compliance? Yes. POST /api/v2/data_compliance/deletion/invitees accepts a list of invitee emails and permanently removes their personal data from Calendly. This supports GDPR right-to-erasure requests without manual intervention in the Calendly dashboard. ### Can I limit what my agent is allowed to do with the Calendly API? Yes. Because you run Jentic One yourself, your own rules decide which Calendly operations and credentials the agent may use. Since Calendly puts the event uuid in the URL path (/scheduled_events/{uuid}/...), you can pin the agent to a single scheduled event so it reads only that event's invitees and nothing else. Higher-impact actions like canceling an event (/scheduled_events/{uuid}/cancellation) or creating webhook subscriptions stay out of reach unless you explicitly add them to the allowed set.