Get Single Contact via Assistable API

Objective: To fetch the specific details of a single contact record. This is essential for verifying data after an update, or retrieving specific attributes (like tags or custom_fields) before triggering a personalized workflow.

1. Endpoint Configuration

HTTP Method: GET
Base URL: https://api.assistable.ai/v2/contacts/
Path Parameter: :id (This corresponds to the specific contact_id)

Full Request URL:

https://api.assistable.ai/v2/contacts/{contact_id}

Critical Distinction: Do not confuse this with the "Get Contacts" (Plural) endpoint.
Get Contact (Singular): Uses {contact_id} to fetch one person.
Get Contacts (Plural): Uses {location_id} to fetch everyone in that location.

2. Payload Preparation

Request Body: None.
Headers: Standard authentication headers (API Key/Bearer Token) are required.

3. Execution Steps

Retrieve Contact ID: Ensure you have the UUID (id) of the specific contact.
Send Request: Execute the GET request using your preferred client.
Validate Response: Ensure the API returns a 200 OK status and a single JSON object.

4. Response Verification

A successful request returns a single contact object.

Success Response Example:

JSON

{
    "id": "3a0b342a-46eb-430a-8ea3-dba2a4d450f7",
    "workspace_id": "test-workspace",
    "location_id": "test-location",
    "first_name": "Jorden",
    "last_name": "Williams",
    "phone_number": "+17702967271",
    "email": "jorden@assistable.ai",
    "tags": [],
    "meta": {},
    "custom_fields": {},
    "attribution": {},
    "integration": {},
    "dnd": {},
    "created_at": "2025-12-03T18:50:51.906176+00:00",
    "updated_at": "2025-12-03T19:07:55.343337+00:00"
}

5. Troubleshooting

404 Not Found:
- The contact_id is invalid or does not exist.
- Common Error: You accidentally provided a location_id instead of a contact_id.
403 Forbidden: The API Key used does not have permission to view this specific contact (e.g., if the contact belongs to a different sub-account/location than the key).