verapli
Sign inJoin free
Menu

Guides · productivity · Popular APIs

Calendly API (personal access token or OAuth app)

Generate a personal access token for internal use, or register an OAuth app in the Calendly developer portal (Sandbox, then a separate Production app) for public integrations.

Researched · not yet run liveLast researched 25 October 2026 · Calendly · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.
Do this with verapliJSON for agents

Who owns what

PATs belong to a Calendly user; OAuth apps belong to a separate Calendly developer account.

  • Calendly user account personalWebhooks and Scheduling API endpoints need a paid plan.
  • Calendly developer account developeroptionalSigns in with GitHub or Google; only for OAuth apps.

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Generate a personal access token (internal use)

    Go to Integrations > API & Webhooks, select Get a token now (or Generate new token), name it, choose scopes and create it.

    • verapli co-pilot
    • Human step: You press submit

    verapli captures CALENDLY_API_TOKEN here by plain code: encrypted in your browser, never shown to AI.

    Where: https://calendly.com/integrations

  2. Sign up for a developer account (public apps)optional

    On developer.calendly.com choose Sign Up and sign in with GitHub or Google.

    • verapli co-pilot
    • Human step: You sign in

    Where: https://developer.calendly.com

  3. Create the OAuth app (Sandbox first)optional

    Create an app with name, kind (web/native), environment, redirect URI and scopes. Use Sandbox for development (localhost http allowed) and a second Production app with an HTTPS redirect URI.

    • verapli co-pilot
    • Human step: You press submit
    • After: Sign up for a developer account (public apps)

    verapli captures CALENDLY_OAUTH_CLIENT_SECRET here by plain code: encrypted in your browser, never shown to AI.

    If something goes wrong (1)
    • Lost the client secret or webhook signing key: They are shown only once and can't be viewed when editing; create a new app or credentials [to verify regeneration]. [2]

    Where: https://developer.calendly.com

Terms and gotchas

Plain-English summary, not legal advice. Each card links its source.

Can cost moneyThe rules say

Webhooks and the Scheduling API need a paid Calendly plan. [3]

What you end up with

Env varSecretFormatWhat it is
CALENDLY_API_TOKENsecretopaque token stringPersonal access token
CALENDLY_OAUTH_CLIENT_IDnot secretopaque id stringOAuth client ID
CALENDLY_OAUTH_CLIENT_SECRETsecretopaque secret stringOAuth client secret
CALENDLY_WEBHOOK_SIGNING_KEYsecretopaque secret stringWebhook signing key for the OAuth app

Pricing

  • Basic API access on any plan; webhooks/Scheduling API on paid plans; some endpoints Enterprise only.

Source [3]

For agents

The same entry as JSON: /api/v1/entries/calendly/api · requirements /api/v1/requirements/calendly/api · terms /api/v1/terms/calendly/api.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for Calendly API (personal access token or OAuth app), and how long will it take?"
  → tools/call requirements { "provider_id": "calendly/api" }

Sources

  1. Personal Access Tokens Create via calendly.com/integrations > API & Webhooks > Get a token now / Generate new token; choose scopes; token unretrievable after creation. · accessed 25 October 2026 · official
  2. Creating an OAuth app Developer account (GitHub or Google sign-in) separate from Calendly account; app name, kind (web or native), environment Sandbox or Production, redirect URI, scopes; start in Sandbox and create a second Production app; Sandbox allows http localhost, Production requires HTTPS; PKCE S256 recommended; Client Secret and Webhook signing key shown only once. · accessed 25 October 2026 · official
  3. Calendly API overview Basic GET/POST on any plan; webhooks and Scheduling API need a paid Professional/Standard or higher plan; some data-deletion and activity-log endpoints Enterprise only. · accessed 25 October 2026 · official
  4. Introduction to the API Internal apps used by your own team should use personal access tokens; public apps for many Calendly users should use OAuth. · accessed 25 October 2026 · official

Provider rules change. This page is generated from verapli registry version 2026.1025.387; spotted something out of date? Tell us. Calendly is not affiliated with verapli.