Follow the procedure below to register and authenticate your public application with the Calendly API v2.
A LastPass account (you can create one here) so the Developer Support team can securely share your application’s OAuth credentials (see Client ID and Client Secret below.)
A Calendly account (you can sign up here) so you can test your integration
Note that Calendly accounts on the free Basic subscription have limited access to the API.
The name of your application (cannot include the word “Calendly”)
Your OAuth redirect URI
This must be HTTPS for web applications unless the URI host is localhost.
For mobile or native applications use a specific redirect_uri, a Proof Key for Code Exchange (PKCE), and S256 for code_challenge_method. For more information on native and mobile authentication, see this guide.
A Client ID and Client Secret
When you register to authenticate with OAuth 2.0, we return to you a Client ID and Client Secret for your application to authenticate with the Calendly API.
Note: If you need to authenticate an internal or private application, see how to authenticate with personal access tokens.
Log in to your LastPass account and generate Sharing Keys.
Register your public application using this form.
After you register your application, you’ll receive its Client ID and Client Secret within one business day from Developer Support.
To initiate the OAuth authorization flow, redirect your user to Get Authorization Code endpoint.
To retrieve the access token, make a POST request to Get Access Token endpoint.
To test the access token, make a call to the Get current user endpoint.