Timezone Handler Setup

List all supported timezones in GoHighLevel. This endpoint returns IANA timezone identifiers that you can use when creating or updating locations, scheduling appointments, and configuring time-sensitive automations. This quick-start covers authentication and retrieving the full timezone list.

Prerequisites

Before making your first Timezone Handler call, confirm you have:

• A GoHighLevel account (agency or sub-account level)
• Access to Settings > Integrations > Private Integrations
• A REST client such as Postman, Insomnia, or curl in your terminal

This is one of the simplest GHL API endpoints. It requires minimal setup and has no location-specific dependencies. You just need a valid token.

Set Up Authentication

The Timezone Handler endpoint requires a Private Integration Token (PIT) with the locations scope.

Navigate to Settings > Integrations > Private Integrations. Click Create New Integration, name it “Timezone API,” and enable the locations scope. Click Save and copy the generated token.

Pass this token in the Authorization header as a Bearer token. Set your base URL to https://services.leadconnectorhq.com. Include the Version: 2021-07-28 header.

Make Your First Call

Retrieve the complete list of supported timezones:

GET /locations/timezones
Authorization: Bearer {your-pit-token}

No query parameters are needed. This returns every IANA timezone identifier that GHL accepts for location configuration, appointment scheduling, and calendar settings.

The response includes standard IANA identifiers like America/New_York, America/Chicago, America/Los_Angeles, Europe/London, Asia/Tokyo, and hundreds more. Use these exact strings when setting the timezone field on location creation or update calls.

This endpoint is read-only. There are no create, update, or delete operations for timezones. The list is maintained by GHL based on the IANA Time Zone Database.

Handle the Response

A successful call returns a 200 status with the timezone list:

{
  "timezones": [
    "Africa/Abidjan",
    "Africa/Accra",
    "Africa/Addis_Ababa",
    "America/Chicago",
    "America/Denver",
    "America/Los_Angeles",
    "America/New_York",
    "Asia/Kolkata",
    "Asia/Tokyo",
    "Europe/London",
    "Europe/Paris",
    "Pacific/Auckland"
  ]
}

The list is alphabetically sorted by region and city. Common US timezones: America/New_York (Eastern), America/Chicago (Central), America/Denver (Mountain), America/Los_Angeles (Pacific). For UTC, use Etc/UTC.

Common errors: 401 means your token is invalid or the locations scope is not enabled. This endpoint rarely fails since it is a static reference list with no input parameters.

Test Your Setup

Run through this checklist to confirm everything works:

1. Fetch the timezone list with GET /locations/timezones
2. Search the response for your local timezone (e.g., America/Chicago)
3. Use a timezone value when creating a location via Location CRUD — set the timezone field to a value from this list
4. Verify the location’s timezone is set correctly in Settings > Business Profile in the GHL dashboard
5. Confirm appointment times display correctly in the location’s local timezone

If a timezone you expect is missing from the list, check for alternate IANA naming. For example, use America/Indianapolis instead of US/Eastern for Indiana.

Next Steps

Read the full Timezone Handler Guide for timezone management across multi-location agencies. From here, explore Location CRUD for creating locations with timezone settings and Location Custom Values for managing location-level configuration.