Create a developer account and your first application

Follow the procedure below to register and authenticate your public application with the Calendly API v2.

Register your OAuth application

  • Sign up for a Calendly developer account using your Github or Google account by clicking the Sign Up button found in the top right corner of this page. Note: This is not your Calendly user account and is not associated with your Calendly user account.

  • Create a new OAuth application

    • Provide name of your application

    • Select the kind of application (web or native)

    • Select your environment that you want to associate your application

      • Sandbox

      • Production

    We recommend starting with Sandbox for development and creating a second application for Production when ready to go live with customer data.

    • Redirect URI: 

      • For the Sandbox environment, we allow HTTP with localhost domain. Example: http://localhost:1234 

      • For the Production environment, this must be HTTPS

  • 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.

  • Proceed into the next step to view/copy your Client Id, Client Secret and Webhook signing key. Be sure to copy these values as you will not be able to access the Client Secret or Webhook signing key again.

Test your application

  1. To initiate the OAuth authorization flow, redirect your user to Get Authorization Code endpoint.

  2. To retrieve the access token, make a POST request to Get Access Token endpoint.

  3. To test the access token, make a call to the Get current user endpoint.

Edit your application

To edit attributes for existing OAuth applications:

  • Click on the OAuth application's menu icon then select "Edit".

  • The following attributes can be edited:

    • Name of app

    • Kind of app

    • Environment type

    • Redirect URI

  • Click "Save".

Please note you will not be able to access the Client Secret or Webhook signing key when editing an OAuth application (these values are only displayed when the OAuth application is created).

See more

Learn what else you can accomplish with the Calendly API.

For more information about conditions that result in an access token being revoked, please see our Frequently Asked Questions.

Copyright Calendly 2024We take the work out of connecting with others so you can accomplish more.Legal