GoHighLevel Calendars API

Update Calendar Resource

PUT/calendars/resources/:resourceType/:id

PUT /calendars/resources/:resourceType/:id Update calendar resource by ID It takes 2 path parameters and 8 body fields, requires the calendars/resources.write scope and authenticates with a sub-account (location) token.

Request and authentication

Method
PUT
Full URL
https://services.leadconnectorhq.com/calendars/resources/:resourceType/:id
Scopes
calendars/resources.write
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

Request body

JSON body fields. Nested objects are shown indented under their parent.

NameTypeDescription
locationIdstring
namestring
descriptionstring
quantitynumber

Quantity of the equipment.

outOfServicenumber

Quantity of the out of service equipment.

capacitynumber

Capacity of the room.

calendarIdsarray

Service calendar IDs to be mapped with the resource. One equipment can only be mapped with one service calendar. One room can be mapped with multiple service calendars.

isActiveboolean

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

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 PUT 'https://services.leadconnectorhq.com/calendars/resources/YOUR_RESOURCETYPE/YOUR_ID' \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  -H 'Version: 2021-07-28' \
  -H 'Content-Type: application/json' \
  -d '{}'

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.

More calendars endpoints