Bug: /contacts/search can’t filter by custom fields (e.g., Relationship Number)

[tylerzastrowghl]

🐛 Describe the Bug

POST /locations/{locationId}/contacts/search ignores filters on custom fields.
Example: filtering on our custom field Relationship Number always returns an empty list, even though the value exists on the contact. Native fields (email, phone) work as expected.

📍 API Endpoint

/locations/{locationId}/contacts/search

✅ Expected Behavior

If I supply a filter on customFields.Relationship Number (or the custom field ID), the endpoint should return the matching contact.

💻 Screenshots or Code Samples

POST /locations/{locationId}/contacts/search
{
"filters": [
{
"field": "customFields.Relationship Number",
"operator": "eq",
"value": "R-123456"
}
],
"limit": 1
}

Product Area

contacts

🧠 Additional Context

Issue affects ~600 k records in our Customer-Success sub-account.

Contact: Tyler Zastrow (Slack @tyler Zastrow / tyler.zastrow@gohighlevel.com).

[tylerzastrowghl]

cc @gauravkanted-ghl

[github-actions]

✅ Issue processed successfully!

Your issue has been reviewed and assigned to the appropriate team.

[shrikantsupekar1]

@tylerzastrowghl
In payload field should be customFields.custom_field_id or customFields.custom_field_key but in example given above you are using customFields.custom_field_name.

[tylerzastrowghl]

@shrikantsupekar1 Thank you so much. I totally missed this and this was the issue!

[kapilmodi]

Task Update: Due date changed to 8 july 2025. Status: Closed.

[kapilmodi]

Task Update: Due date changed to 8 july 2025. Status: Closed.