[Bug Report: API Field Missing] #126
Description
🐛 Describe the Bug
The API endpoint is missing the timeZoneId field, which is visible and editable in the HighLevel UI for contacts. This field is important for storing and retrieving a contact’s time zone programmatically, but it is not returned in the API response for contacts, nor is it accepted in API updates.
📍 API Endpoint
/contacts/{id}, /contacts, /contacts/upsert
✅ Expected Behavior
The API should include the timeZoneId field in both:
The GET /contacts/{id} response (if the value exists for that contact)
The POST/PUT/PATCH /contacts and /contacts/upsert request/response so we can set or update the value.
💻 Screenshots or Code Samples
// Expected to see something like this in API responses:
{
"id": "abc123",
"firstName": "John",
"lastName": "Doe",
"email": "john@example.com",
"timeZoneId": "America/New_York"
}
Product Area
contacts
📋 Use Case
We need this field to:
Store the contact’s time zone when creating or updating contacts.
Use the value to schedule messages and workflows at the correct local time for the contact.
Synchronize contact data between HighLevel and external systems.
Without this field in the API, we can’t programmatically keep time zones aligned with contact records.
🚨 Why Should This Be Prioritized?
This is blocking our ability to:
Accurately schedule communications per contact’s local time.
Sync time zone data from other systems into HighLevel automatically.
Maintain consistent and accurate contact information across platforms.
This is affecting all our integrations that depend on time zone logic and requires manual updates, reducing automation efficiency.
🧠 Additional Context
The field appears in the HighLevel UI but is absent from the API schema and payloads.
We have tested multiple endpoints (/contacts, /contacts/upsert, /contacts/{id}) and confirmed the field is not returned or accepted.
This impacts both Zapier and direct API integrations.
==================
Actual Behavior
The timeZoneId field is ignored or results in "Invalid field" error.
Contact is created/updated without storing the time zone.
Expected Behavior
The API should accept and store timeZoneId just like other fields.
The value should persist and appear in GET /contacts/{id}.
