Calendly API

Calendly's REST API for managing scheduling links, event types, scheduled events, and invitees to automate appointment booking workflows.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Other calendly scheduling booking calendar meetings rest-api oauth webhooks
⚙ Agent Friendliness
58
/ 100
Can an agent use this?
🔒 Security
83
/ 100
Is it safe for agents?
⚡ Reliability
82
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
--
Documentation
78
Error Messages
72
Auth Simplicity
80
Rate Limits
75

🔒 Security

TLS Enforcement
100
Auth Strength
80
Scope Granularity
75
Dep. Hygiene
80
Secret Handling
78

Scheduling API. OAuth2 + PAT. Meeting attendees are PII. Webhook signing for event verification. OAuth tokens expire — handle token refresh in agents.

⚡ Reliability

Uptime/SLA
85
Version Stability
82
Breaking Changes
80
Error Recovery
80
AF Security Reliability

Best When

An agent needs to react to Calendly bookings or manage invitees as part of a sales, onboarding, or support workflow.

Avoid When

You need to create or modify event types programmatically, or need complex resource management.

Use Cases

  • Reading scheduled events and invitee data from agent workflows
  • Creating single-use scheduling links programmatically
  • Monitoring new bookings via webhooks for agent follow-up actions
  • Canceling or rescheduling events via automation
  • Reporting on scheduling data and meeting patterns

Not For

  • Teams not using Calendly
  • Creating event types (only management of existing ones)
  • Complex multi-resource booking (rooms, equipment)
  • Teams needing open-source self-hosted scheduling

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
Yes

Authentication

Methods: oauth2 api_key
OAuth: Yes Scopes: Yes

OAuth2 required for production use and accessing other users' data. Personal access tokens available for single-user automations. OAuth is recommended for multi-user apps.

Pricing

Model: freemium
Free tier: Yes
Requires CC: No

API access requires Standard plan or above for most meaningful use. Free plan API access is very limited. Teams plan needed for admin-level API capabilities.

Agent Metadata

Pagination
cursor
Idempotent
No
Retry Guidance
Not documented

Known Gotchas

  • Rate limit of 250 req/hour is very restrictive for agents processing many bookings
  • Cannot create event types via API — only manage existing ones
  • OAuth2 required for accessing data beyond single user — no simple admin key
  • Webhook challenge verification required for subscription registration
  • Event UUIDs are URIs (prefixed with namespace) — not simple UUIDs
  • Paid plan required for most useful API capabilities (Standard or above)

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Calendly API.

$99

Scores are editorial opinions as of 2026-03-06.

5174
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered