Contacts
Get contact
Retrieves a single contact by its numeric contact_id. The full contact record is returned in payload, including name, email, phone_number, identifier, additional_attributes, custom_attributes, and activity timestamps such as last_activity_at and created_at. Obtain a contact_id from GET /api/ext/omni_v2/contact or GET /api/ext/omni_v2/contact/search.
curl --request GET \
--url 'https://api.nabrah.ai/api/ext/omni_v2/contact/<contact_id>' \
--header 'X-API-Key: <your-api-key>'{
"payload": {
"id": 0,
"additional_attributes": {
"city": "string",
"country": "string",
"description": "string",
"company_name": "string",
"country_code": "string",
"social_profiles": {}
},
"availability_status": "string",
"email": "string",
"name": "string",
"phone_number": "string",
"blocked": false,
"identifier": "string",
"thumbnail": "string",
"custom_attributes": {},
"last_activity_at": 0,
"created_at": 0
}
}Authentication
Send your Web API key (prefix nb_) in the X-API-Key header. The key is scoped to one project; the contact must belong to that project.
Where the contact_id comes from
Call GET /api/ext/omni_v2/contact to list contacts or GET /api/ext/omni_v2/contact/search to look one up by name, email, or phone. Each returned contact's id is the value to pass as contact_id here. A contact you just created via POST /api/ext/omni_v2/contact exposes its id at payload.contact.id.
Authorization
X-API-KeystringheaderrequiredYour workspace API key. Create one in the dashboard under API keys.
Path parameters
contact_idintegerrequiredNumeric identifier of the contact to retrieve.
Obtained from the list (GET /api/ext/omni_v2/contact) or search (GET /api/ext/omni_v2/contact/search) endpoints — use the id field of a contact.
Response
Successful Response
application/json
Validation Error
application/json