GoHighLevel Calendars API

Validate Groups Slug

POST/calendars/groups/validate-slug

POST /calendars/groups/validate-slug Validate if group slug is available or not It takes 2 body fields, requires the calendars/groups.write scope and authenticates with a sub-account (location) token.

Request and authentication

Method: POST
Full URL: https://services.leadconnectorhq.com/calendars/groups/validate-slug
Scopes: calendars/groups.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

Request body

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

Name Type Description

locationIdrequired

string

Location Id

Example: ve9EPM428h8vShlRW1KT

slugrequired

string

Slug

Example: calendar-1

Response fields

Top-level fields returned on a successful call.

Name	Type	Description
`available`required	`boolean`	—

Example request

Copy-paste ready. Swap YOUR_TOKEN for your access token or Private Integration Token.

curl -X POST 'https://services.leadconnectorhq.com/calendars/groups/validate-slug' \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  -H 'Version: 2021-07-28' \
  -H 'Content-Type: application/json' \
  -d '{
    "locationId": "ve9EPM428h8vShlRW1KT",
    "slug": "calendar-1"
  }'

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 pricing Read the setup guide

More calendars endpoints