Quickstart

Get a token

Tokens are created by an administrator of your Sailer workspace — anyone with the Configuration permission — in Company Profile → API. Ask them for one scoped to what you plan to build. Create and manage API tokens walks through it, and Authentication has the scope list.A token looks like sk_live_AbC123.xYz789.... It is shown once, at creation, and stored only as a hash — so put it somewhere safe. A lost token cannot be recovered, only replaced.

Confirm it works

GET /v1/me describes the token itself. It is the cheapest way to check that authentication is wired up correctly.

curl https://api.chatsailer.com/v1/me \
  -H "Authorization: Bearer $SAILER_API_TOKEN"

The response tells you which workspace the token belongs to and which scopes it carries. There is no tenant header to set: the workspace is implied by the token.

Read some contacts

curl "https://api.chatsailer.com/v1/contacts?limit=5" \
  -H "Authorization: Bearer $SAILER_API_TOKEN"

{
  "data": [
    {
      "object": "contact",
      "id": "con_...",
      "first_name": "Ana",
      "last_name": "Ribeiro",
      "email": "ana@example.com",
      "phone": "+5511999999999",
      "status": "open",
      "external_id": null,
      "custom_fields": { "segment": "enterprise", "annual_revenue": null },
      "created_at": "2026-08-14T12:04:11Z",
      "updated_at": "2026-08-29T09:31:52Z"
    }
  ],
  "meta": { "limit": 5, "has_more": true },
  "links": { "next": "eyJhZnRlciI6W1sic..." }
}

Pass links.next back as cursor to read the next page. See Pagination.

Create one

curl -X POST https://api.chatsailer.com/v1/contacts \
  -H "Authorization: Bearer $SAILER_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"first_name": "Bruno", "phone": "+5511987654321", "email": "bruno@example.com"}'

This needs the contacts:write scope. first_name and phone are required; phone is unique per workspace and stored as E.164. If your token lacks the scope you get a 403 naming exactly what is missing — see Errors.

Authentication

Scopes, and the two limits worth knowing up front.

API Reference

Every endpoint, with a playground.

Getting started

Working with the API

Next

Authentication

API Reference

​Next

Authentication

API Reference

Next