[Bug Report: API Field Missing] Contacts response customField key

[Cobeas]

🐛 Describe the Bug

I keep making useless requests to the /customFields endpoint just so I can find a customField_id by the key and then finding that Id at the contact level (/contacts/search response) so that it can be used in multiple sub-accounts.

📍 API Endpoint

/contacts/search

✅ Expected Behavior

The API should include the custom_field_key next to the Id and value

💻 Screenshots or Code Samples

Current customFields response in /contacts/search

{
id: "some_id",
value: "string"
}

Expected:

{
key: "custom_field_key",
id: "some_id",
value: "string"
}

Product Area

contacts

📋 Use Case

We need this field to:

• Make less calls to the API
• Write more efficient code

🚨 Why Should This Be Prioritized?

This should be prioritized because:

• It would be an easy fix

🧠 Additional Context

No response

[github-actions]

✅ Issue processed successfully!

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

[kapilmodi]

Task Update: Due date changed to 8 october 2025. Status: todo.

[kapilmodi]

Task Update: Due date changed to 8 october 2025. Status: todo.

[gauravponkiya]

We’re unable to support your request. The required information isn’t stored in a single location. The Contacts API has a single responsibility — to manage and return contact-related data.

You can use the existing Get Custom Fields or Get Custom Field IDs APIs to retrieve any additional data related to custom fields. Custom field information will not be included in the Contacts API response.

[kapilmodi]

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