Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.alterauth.com/llms.txt

Use this file to discover all available pages before exploring further.

Overview

Connect your users to Calendly for scheduling automation, event management, and availability tracking.
PropertyValue
Provider IDcalendly
CategoryProductivity
PKCESupported
Token refreshAutomatic
Redirect URIShown in Developer Portal

Step 1: Create a Calendly OAuth App

1

Sign up for the Calendly Developer Portal

Go to developer.calendly.com and sign up with GitHub or Google. The developer account is separate from a regular Calendly user account.
2

Create an application

Open My OAuth Apps and click Create New App.
3

Configure your app

Choose:
  • Application type (web or native)
  • Environment — Sandbox for development (HTTP localhost allowed), Production for live data (HTTPS only)
4

Add the redirect URI

Add the Redirect URI from the Developer Portal to the Redirect URI field.
5

Get your credentials

Copy the Client ID, Client Secret, and Webhook signing key. The secret and signing key are only displayed once.
Never share your Client Secret publicly. Store it securely and only enter it in the Alter Vault Developer Portal.

Step 2: Add to Alter Vault

1

Open the Developer Portal

Go to portal.alterauth.com and navigate to your app.
2

Add Calendly provider

Go to OAuth Providers > Add Provider > Calendly.
3

Enter credentials

  • Client ID: Paste your Calendly Client ID
  • Client Secret: Paste your Calendly Client Secret
4

Select scopes

Choose the scopes your app needs.
5

Save

Click Save. The provider is now active.

Available Scopes

ScopeDescription
defaultAccess to Calendly scheduling data including events, invitees, and availability

Notes

  • The Calendly developer account is separate from a regular Calendly user account — sign in with GitHub or Google.
  • Use the Sandbox environment for development; HTTP localhost redirect URIs are allowed there. Production requires HTTPS.
  • Calendly OAuth recommends PKCE with the S256 code_challenge_method (RFC 7636).
  • The Client Secret and Webhook signing key are revealed only at creation — save them immediately.