List appointments.

GET/api/v1/calendars/appointments

Browse API endpoints

Calendar and booking / CRM REST API

Scope: appointments:read

Each returned appointment includes the linked contact's first name, last name, email, and phone, and no date range is required. Grant this scope only where the caller is meant to see customer details; a booking integration that answers "when are you free?" wants availability:read instead.

Query parameters:

calendarId - Filter by calendar
startDate - Start of date range (Unix timestamp, milliseconds)
endDate - End of date range (Unix timestamp, milliseconds)
status - scheduled, confirmed, completed, cancelled, no_show
limit - Max results (default 50, max 100)

Loading endpoint details...

Build a request

Request example

Documented defaults and example values are ready. Change only the parameters you need.

Connection

Your CRM deployment URL

Replace the Bearer API key placeholder in the copied server-side code. No API key is entered or sent here.

Sub-account ID Agency keys onlyAgency-scoped keys require the X-Sub-Account-Id header.

Query parameters

calendarId - Filter by calendar

startDate - Start of date range (Unix timestamp, milliseconds)

endDate - End of date range (Unix timestamp, milliseconds)

status - scheduled, confirmed, completed, cancelled, no_show

limit - Max results (default 50, max 100)

cURL

curl --request GET \
  --url 'https://your-crm.example.com/api/v1/calendars/appointments?limit=50' \
  --header 'Authorization: Bearer <YOUR_API_KEY>'

This shows a static response from the documentation. It does not send a request to your CRM or use an API key.