Skip to main content
1

Get a token

Tokens are created by an administrator of your Sailer workspace — anyone with the Configuration permission. Ask them for one scoped to what you plan to build; see Authentication for 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.
2

Confirm it works

GET /v1/me describes the token itself. It is the cheapest way to check that authentication is wired up correctly.
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.
3

Read some contacts

Follow links.next to page through the rest. See Pagination.
4

Create one

This needs the contacts:write scope. If your token lacks it you get a 403 naming exactly what is missing — see Errors.

Next

Authentication

Scopes, and the two limits worth knowing up front.

API Reference

Every endpoint, with a playground.