Native Calendar API

Booking is the one capability that needs somewhere to put the appointment. A sub-account without a CRM books into a Team Follow Up calendar, described in Calendars and booking. Availability comes back as days of ISO start times and a booking answers with the time it actually took, which is the same shape the GoHighLevel path uses, so one integration reads either. Every operation takes locationId as a query parameter, and access is re-checked against it on each call.

Calendars

Endpoint	Use it to
List calendars	Every bookable calendar, optionally with how much of the next N days is taken.
Create a calendar	Define hours, slot length, notice and lookahead.
Get a calendar	One calendar, as the engine reads it.
Update a calendar	Change settings. The merged calendar is validated, not the patch.
Delete a calendar	Retire it. Refuses while people still have appointments, unless forced.

Availability

Endpoint	Use it to
Get free slots	What this calendar can offer, day by day. Never cached.
Preview slots for a calendar definition	What a definition WOULD offer, before saving it.

Appointments

Endpoint	Use it to
List appointments for a contact	Everything booked for one person.
Book an appointment	Claim a seat for a contact.
List appointments in a window	What is booked between two times, for a diary view.
Cancel an appointment	Free the seat and stop its reminders.
Confirm an appointment	Record a confirmation that did not arrive on a call.
Reschedule an appointment	Move it, re-anchoring its reminders.
Add an event	Hold time that is not a lead: a meeting, a reminder.

Connected calendar systems

Endpoint	Use it to
List calendar connections	Which systems are offered, and which this sub-account has connected.
Connect a calendar system	Store a pasted credential, and register for cancellations.
Disconnect a calendar system	Forget it and unregister.
List linked calendars	The calendars that live in that product.
List linked bookings	What is booked there, in a window.

Scopes: projects:read and projects:write. Calendars have no scope of their own: a calendar belongs to a sub-account, so a key that can read and write projects can work its calendars. See Authentication.

Guides

Calendars and booking.
Why the agent found no times, which is the first place to look when a diary reads as empty.
Contacts without a CRM for the people being booked.

Agents

Split Testing

Skills & Tools

Campaigns

Campaign Workflows

Calls

Analytics

Billing

Projects

Power Dialer

Contacts

Native Contacts

Native Calendar

Phone Numbers

Voices

GHL

Calendars

Availability

Appointments

Connected calendar systems

Guides

​Calendars

​Availability

​Appointments

​Connected calendar systems

​Guides

Calendars

Availability

Appointments

Connected calendar systems

Guides