Get contact by ID
GET /api/contacts/{id}
Retrieves a single contact by its unique identifier, including all known information such as name, email, phone, company, and resolution status.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The unique identifier of the contact to retrieve.
Responses
Section titled “ Responses ”The contact was found and returned.
A contact represents an individual person who has communicated with your organization. Contacts are automatically created when a new sender is detected, and enriched over time with additional information from conversations and account resolution.
object
Unique identifier for the contact.
Example
ct1a2b3c-5678-9abc-def0-1234567890abThe tenant this contact belongs to.
Example
a0b1c2d3-4567-89ab-cdef-0123456789abExternal CRM identifier. Set when this contact is resolved against a CRM system via an MCP server.
Example
CRM-CONTACT-78291How the contact was identified. ‘unresolved’ means no CRM match was found yet. ‘crm_resolved’ means the contact was matched to a CRM record via an MCP server. ‘manually_resolved’ means a human agent linked the contact manually.
Example
crm_resolvedFirst name of the contact.
Example
AlexLast name of the contact.
Example
DoePrimary email address of the contact.
Example
alex.doe@example.comThe email address the visitor typed in a live chat, at its start or in the email field the chat shows. It is not verified. Present only when the visitor gave one.
Example
alex.doe@example.comPhone number of the contact in E.164 format.
Company name associated with this contact, derived from email domain or CRM resolution.
Example
Example CompanyTimestamp when the contact was first detected.
Example
2026-02-10T14:30:00.000ZTimestamp when the contact was last updated.
Example
2026-03-20T09:15:00.000ZNo contact exists with the given ID in the authenticated tenant.
Standard error response returned by all endpoints on failure.
object
A human-readable error message describing what went wrong.
Example
Conversation not foundA machine-readable reason on some refusals, for example ‘key_lock’ when an API key’s brand or workspace restriction does not cover the action.
Example
key_lockOn a 403 for an API key without a scope the endpoint requires: the scopes the key lacks.
Example
[ "mcp:write"]On a 409 with code duplicate_question or duplicate_rule_text: the knowledge base entry or policy that already holds the question or rule text.
Example
11223344-5566-4788-99aa-bbccddeeff00On a 422 about one MCP connection a request names, from an assignment or an agent create or update (a connection that does not exist, one listed twice, or one that does not declare a tool named): the connection, as the request named it.
On the same 422: the tool names the connection does not declare.
Example
[ "get_orders"]On the same 422: the tools the connection declares.
Example
[ "get_order", "search_orders"]