Skip to main content
The Sayless public API lets personal API keys, OAuth user tokens, and OAuth app actors read and mutate the work graph: conversations, messages, tickets, companies, contacts, documents, teams, attachments, and outbound webhooks. It is not a full clone of every in-app Settings or Analytics screen. Billing, insights dashboards, channel connect wizards, and the official client sync protocol stay in the product (session cookie).

​
Base URL

Most resources use POST action routes, for example POST /api/v1/tickets/list and POST /api/v1/tickets/create. The TypeScript SDK maps these to methods such as client.tickets.list().

​
Resource guides

​
What is in scope

​
What is app-only

These stay in the Sayless product (session cookie). API keys cannot call them:
  • Sync / bootstrap / delta (official client protocol)
  • Billing and plan checkout
  • Channel connect settings (Slack, Telegram, email domain setup, …)
  • Broadcasts and broadcast profiles
  • Triggers and CSV imports
  • Analytics dashboards and insights
  • Meetings / Gong tooling
  • Issue-tracker tool proxy endpoints (browse another tracker through Sayless — use that product’s own APIs; link from the app)
  • Customer portal admin
  • Creating or listing API keys (use Settings → Access for personal keys)

​
Auth

See Authentication.

​
Stability

See Stability and versioning.

​
Next