GoHighLevel Calendars API

Get Calendar Resource

GET/calendars/resources/:resourceType/:id

GET /calendars/resources/:resourceType/:id Get calendar resource by ID It takes 2 path parameters, requires the calendars/resources.readonly scope and authenticates with a sub-account (location) token.

Request and authentication

Method
GET
Full URL
https://services.leadconnectorhq.com/calendars/resources/:resourceType/:id
Scopes
calendars/resources.readonly
Token type
Sub-account (location) token
Accepted auth
OAuth Access Token, Private Integration Token
API version header
Version: 2021-07-28
Schema verified
22 June 2026

Path parameters

Substituted into the URL. Required by definition.

NameTypeDescription
resourceTyperequiredstring

One of: equipments, rooms

idrequiredstring—

Response fields

Top-level fields returned on a successful call.

NameTypeDescription
locationIdrequiredstring

Location ID of the resource

namerequiredstring

Name of the resource

Example: yoga room

resourceTyperequiredstring

One of: equipments, rooms

isActiverequiredboolean

Whether the resource is active

descriptionstring

Description of the resource

quantitynumber

Quantity of the resource

outOfServicenumber

Indicates if the resource is out of service

Example: 0

capacitynumber

Capacity of the resource

Example: 85

calendarIdsrequiredarray

Calendar IDs

Example: Jsj0xnlDDjw0SuvX1J13,oCM5feFC86FAAbcO7lJK

Example request

Copy-paste ready. Swap YOUR_TOKEN for your access token or Private Integration Token, and the sample IDs for your own.

curl -X GET 'https://services.leadconnectorhq.com/calendars/resources/YOUR_RESOURCETYPE/YOUR_ID' \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  -H 'Version: 2021-07-28'

Skip the schema lookup

Hylo gives your AI agent this schema — and the other 52 documented here — without you looking anything up. Ask in plain English; it picks the endpoint, fills the body, and can run the call against your own sub-account.

View pricingRead the setup guide

More calendars endpoints