GoHighLevel Calendars API
Create Calendar Resource
/calendars/resources/:resourceTypePOST /calendars/resources/:resourceType Create calendar resource by resource type It takes 1 path parameter and 7 body fields, requires the calendars/resources.write scope and authenticates with a sub-account (location) token.
Request and authentication
- Method
POST- Full URL
https://services.leadconnectorhq.com/calendars/resources/:resourceType- 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.
| Name | Type | Description |
|---|---|---|
resourceTyperequired | string | One of: |
Request body
JSON body fields. Nested objects are shown indented under their parent.
| Name | Type | Description |
|---|---|---|
locationIdrequired | string | — |
namerequired | string | — |
descriptionrequired | string | — |
quantityrequired | number | Quantity of the equipment. |
outOfServicerequired | number | Quantity of the out of service equipment. |
capacityrequired | number | Capacity of the room. |
calendarIdsrequired | array | 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. |
Response fields
Top-level fields returned on a successful call.
| Name | Type | Description |
|---|---|---|
locationIdrequired | string | Location ID of the resource |
namerequired | string | Name of the resource Example: |
resourceTyperequired | string | One of: |
isActiverequired | boolean | Whether the resource is active |
description | string | Description of the resource |
quantity | number | Quantity of the resource |
outOfService | number | Indicates if the resource is out of service Example: |
capacity | number | Capacity of the resource Example: |
calendarIdsrequired | array | Calendar IDs Example: |
Example request
Copy-paste ready. Swap YOUR_TOKEN for your access token or Private Integration Token, and the sample ID for your own.
curl -X POST 'https://services.leadconnectorhq.com/calendars/resources/YOUR_RESOURCETYPE' \
-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
- Create CalendarPOST /calendars/
- Create Event NotificationPOST /calendars/:calendarId/notifications
- Create SchedulePOST /calendars/schedules
- Edit Block SlotPUT /calendars/events/block-slots/:eventId
- Fetch Calendar ResourcesGET /calendars/resources/:resourceType
- Find Event NotificationGET /calendars/:calendarId/notifications/:notificationId
- All GoHighLevel Calendars endpointsCategory index
- GoHighLevel API referenceEvery category, webhooks, and OAuth scopes