Skip to main content
Your team already works in Sailer. These docs are how your code and your agents do the same.

REST API

Your backend talks to api.chatsailer.com. Tokens, /v1, a playground.

MCP

Claude, ChatGPT, or Cursor talks to mcp.chatsailer.com. No code.
Pick the surface that matches who is calling. Mixing them is allowed — they read the same workspace — but they do not share a hostname, a protocol, or an auth story.

​
REST API

The Sailer API lets you read and write the same records your team works with in the product: contacts, organizations, deals, the conversations they are having, and the campaigns they belong to.
Early access. The /v1 contract below is stable and versioned, but not every resource is live yet. This page lists what you can call today.

​
Available today

Notes, activities, and tags are part of the /v1 design and will appear here as they ship. There is no public send: conversations are read-only, and messages:write is unwired.
Enrolling a contact in a campaign or audience sends real messages on the campaign’s schedule. That cannot be recalled. See POST /v1/campaigns/{campaign_id}/participants and POST /v1/audiences/{audience_id}/members.

​
Start here

Quickstart

Your first authenticated request, in about two minutes.

Authentication

Token format, scopes, and what a token can and cannot reach.

Pagination

One cursor scheme across every collection.

Errors

The error envelope and how to handle each type.

​
Base URL

Every endpoint is under /v1. The version is in the path, so a future /v2 can land without breaking anything you build today.

​
MCP

Two hosted servers. Connect one, ask in plain language, watch the model call tools against a real workspace. First connection is read-only on purpose. Start at MCP, then pick a client tutorial.