Calendly

Tier

Calendly's docs describe creating an OAuth app in the developer console and using it at once, with no review, verification or listing step.

Using Composio?

Composio has a managed Calendly OAuth app, so you can prototype without registering your own. Register your own Production app before launch so your app name is on the consent screen. The separate 'Calendly MCP' toolkit needs your own app.calendly

Sandbox app

Users see: Calendly's standard consent screen showing your app name and the scopes you request.Next: Create a second app with the Production environment and an HTTPS redirect URI.Docs1

Production app

Users see: Calendly's standard consent screen showing your app name and the scopes you request.Docs1, 3· medium confidence

New OAuth apps get no API access until you select scopes. Calendly lists 23 scopes, and each :write scope includes the matching :read. The docs mention no scope that needs extra approval from Calendly. Apps created before scopes were introduced keep full access.

• users:read, scheduled_events:read, event_types:readbasicRead the user's profile, booked meetings and event types. Nothing beyond user consent
• webhooks:writebasicCreate webhook subscriptions. No review, but it only works if the user has a Standard, Teams or Enterprise plan
• organizations:write, data_compliance:write, activity_log:readbasicOrg admin, data deletion and audit log access. No review is documented. Some of these endpoints are Enterprise-only or need an org admin

• 'An error has occurred: the requested scope is invalid, unknown or malformed'

  The authorize URL asks for scope names that are not enabled on the app, or that are formatted wrongly (commas, dot-style names, stray characters).

  FixUse exactly the scope names enabled on the app, separated by spaces.

  Community6· medium confidence

• Webhook subscription creation fails for some users

  Webhooks need the user to be on a Standard, Teams or Enterprise plan.

  FixCheck the user's plan, or fall back to polling the API for users on Free.

  Docs3

• Connected users suddenly get 401 errors

  Calendly revokes tokens when the user changes their login email, password or login method.

  FixHandle 401 errors by asking the user to reconnect.

  Docs3· medium confidence

• Does anyone at Calendly approve the scopes on a new app, or do they only need user consent?

  The scopes page says access needs scopes 'requested and approved' but does not name the approver. No source describes a Calendly review.

  ResolveCreate a Production app with your scopes and check that a different Calendly account can connect right away.

• Are there connection caps, or other differences between Sandbox and Production apps besides redirect URI rules?

  The docs only describe the redirect URI difference.

  ResolveCheck the developer console or ask in the Calendly community's API & Webhook Help forum.

1. 1Creating an OAuth appCalendly developer docs · Official docs · checked 27 Oct 2026
2. 2Authorization ScopesCalendly developer docs · Official docs · checked 27 Oct 2026
3. 3Frequently asked questionsCalendly developer docs · Official docs · checked 27 Oct 2026
4. 4How to register your own Calendly API OAuth appNango docs · Community · checked 27 Oct 2026
5. 5Managed auth toolkitsComposio docs · Composio docs · checked 27 Oct 2026
6. 6The requested scope is invalid unknown or malformedCalendly Community · Search results · not yet checked
7. 7Missing required parameter code verifierCalendly Community · Search results · not yet checked
8. 8Rate LimitsCalendly developer docs · Search results · not yet checked