Calendly API Documentation

This is the complete API documentation for connecting to the Calendly API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.

MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.

Meet Calendly: Schedule meetings, share booking links, automate reminders, and route invitees. Keep reading to get started.

Quickstart

Before you run your first Calendly request, you need three things:

1. A MindCloud account — sign in or create an account at MindCloud.
2. A MindCloud API Key — create one in API Keys. Keep it on your server.
3. At least one Calendly connection — create or choose one in Connections. Note its connectionId.

Every Calendly action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/calendly/latest/actions/{actionSlug}

You need a MindCloud API Key and a Calendly connection. Then call an action such as Get Current User:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/calendly/latest/actions/get-current-user" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

Every response comes back in the same envelope, with your rows in a data array:

{
  "success": true,
  "data": [
    { "id": "1042", "name": "Ava" }
  ],
  "meta": {}
}

After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.

Authentication

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Calendly account that should run the action. MindCloud stores and refreshes the Calendly credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.

Calendly actions

All 26 published actions for this Calendly version. Each page documents the endpoint, arguments, and response controls.

• POSTCancel Event
• POSTCreate Event Invitee
• POSTCreate Invitee No Show
• POSTCreate One-Off Event Type
• POSTCreate Single-Use Scheduling Link
• POSTCreate Webhook Subscription
• DELETEDelete Webhook Subscription
• GETGet Current User
• GETGet Event Invitee
• GETGet Event Type
• GETGet Invitee No Show
• GETGet Routing Form
• GETGet Scheduled Event
• GETGet Webhook Subscription
• GETList Event Invitees
• GETList Event Type Available Times
• GETList Event Types
• GETList Organization Memberships
• GETList Routing Form Submissions
• GETList Routing Forms
• GETList Scheduled Events
• GETList User Availability Schedules
• GETList User Busy Times
• GETList Webhook Subscriptions
• POSTSubmit Routing Form
• DELETEUnmark Invitee No Show

Related apps

More Marketing apps on the Universal API, behind the same REST shape. Or browse all apps.

Google FormsMailchimpWebflowGoogle AdsActiveCampaignBrevoMailerLiteKit