Calendly
Generated live by the research agent (Gemini), checked 2026-10-19. Setup not tested by hand.
Building an OAuth integration with Calendly requires setting up an application within their developer ecosystem and configuring authentication flows such as PKCE. Official documentation outlines standard rate limits and developer policies, but specific details regarding public app review wait times are not documented in the provided sources.
Not enough evidence to rate
- Hands-on work
- 1+ hour
- Waiting for approval
- Unknown
- Confidence
- low
Assumes: A public app that any external user can connect, requesting the scopes an AI agent typically needs to read and act on the user's data.
The agent couldn’t establish 7 of the 7 facts that set difficulty, so it won’t guess a tier. Known hurdles put it at tier 1 or higher. Check the provider’s developer docs directly, or regenerate later.
Solid dark bar: your hands-on work. Amber: the minimum wait. Hatched: the range sources disagree on, or an open-ended wait.[2]
What we know so far. Nothing gates this path. 7 facts unknown, so the tier could be higher.
| Self-serve credentials | Unknown | The sources discuss obtaining authorization codes and endpoints but do not explicitly detail the self-serve developer account creation process.[2] |
|---|---|---|
| Limits until reviewed | Unknown | Rate limits are specified for APIs, but unreviewed development mode user caps or restrictions are not mentioned.[1] |
| Provider review | Unknown | The sources do not detail whether an app review process is mandatory before external users can connect. (no source) |
| Security assessment | Unknown | Security and encryption requirements are mentioned in developer guidelines, but a formal third-party security assessment requirement is not detailed.[3] |
| Business verification | Unknown | Business verification requirements are not mentioned in the official sources. (no source) |
| Mandatory fees | Unknown | The sources do not mention whether any fees apply to creating an OAuth app or accessing the API. (no source) |
| Partner or paid access | Unknown | Whether the developer program or specific scopes are gated behind a waitlist or partner status is not stated. (no source) |
You can start today without any of this. Composio already provides a managed OAuth app for Calendly (calendly, calendly_mcp), so users can connect while you work through your own app. You need your own app for your brand on the consent screen, your own rate limits, or scopes beyond the defaults. Managed auth list
Steps
Agent steps an AI agent can do or draft for you. You steps that need your identity, accounts, legal authority or a real demo.
Configure OAuth Authorization Flow
AgentImplement the authorization code flow or the recommended PKCE flow by directing users to Calendly's authorization endpoint with the required client_id, redirect_uri, and code_challenge.[2]
What you will need
Nuances that catch people out
- Only 8 OAuth tokens per user can be requested within a span of 1 minute.[1]
Evidence
What we could not verify
- Exact hands-on hours required are estimated as specific implementation times are not provided in the sources.
- Calendar wait times for app approval are completely unknown.
- Whether self-serve credentials are immediately available upon signup is not explicitly stated.
Sources
Each quote was checked by code against the live page. “Not found on page” means the quote may be paraphrased, so treat that claim with care.
- Rate Limits | Calendly | Developer DocumentationProvider docsQuote found on pagechecked 2026-10-19
Only 8 OAuth tokens per user can be requested within a span of 1 minute.
- Get Authorization Code | Calendly | Developer DocumentationProvider docsQuote found on pagechecked 2026-10-19
While this flow is supported, we recommend using the PKCE flow for all OAuth applications.
- Developer Policy — Security, Data Use & Integration Guidelines | CalendlyProvider docsQuote found on pagechecked 2026-10-19
All Developers must have an industry standard privacy policy in place that accurately describes the specifics of data usage and meets applicable legal and consent requirements.