List contacts.

GET/api/v1/contacts

Browse API endpoints

Contacts / CRM REST API

Scope: contacts:read

Query parameters:

search - Full-text search (name, email, company)
email - Exact email match. Returns array with single contact or empty array. More efficient than search for programmatic lookups.
limit - Max results (default 50, max 100)
cursor - Pagination cursor
lifecycleStage - Filter by stage
source - Filter by lead source
tags - Comma-separated tag filter (e.g., tags=vip,enterprise)
assignedTo - Filter by team member ID
hasPhone - true to only return contacts with phone numbers

Response:

Code example

{
  "data": [
    /* contacts */
  ],
  "meta": { "total": 150, "hasMore": true, "cursor": "..." }
}

Loading endpoint details...

Build a request

Request example

Documented defaults and example values are ready. Change only the parameters you need.

Your CRM deployment URL

Replace the Bearer API key placeholder in the copied server-side code. No API key is entered or sent here.

Sub-account ID Agency keys onlyAgency-scoped keys require the X-Sub-Account-Id header.

search - Full-text search (name, email, company)

email - Exact email match. Returns array with single contact or empty array. More efficient than search for programmatic lookups.

limit - Max results (default 50, max 100)

cursor - Pagination cursor

lifecycleStage - Filter by stage

source - Filter by lead source

tags - Comma-separated tag filter (e.g., tags=vip,enterprise)

assignedTo - Filter by team member ID

hasPhone - true to only return contacts with phone numbers

cURL

curl --request GET \
  --url 'https://your-crm.example.com/api/v1/contacts?limit=50' \
  --header 'Authorization: Bearer <YOUR_API_KEY>'

This shows a static response from the documentation. It does not send a request to your CRM or use an API key.