Skip to main content
All requests are authorized with a bearer token:
Tokens are stored as SHA-256 hashes and compared in constant time.

Workspace keys (sa_live_…)

Grant access across the whole workspace. Authorization is governed by scopes on the key:
A key needs an explicit scope: one with no scopes is refused everywhere (403 insufficient_scope). Reads require read (or *), writes require write (or *), and tracking requires track, write or *.

MCP connector tokens

When you connect an AI assistant through the MCP server, Affixo mints a key for that connection. It works for reads and configuration, but it can never touch money, even when it carries the write scope. These calls refuse it with 403 insufficient_scope and "need": "financial":
  • POST /v1/track/* (click, lead, sale and refund)
  • PATCH /v1/commissions/{id}
  • PATCH /v1/conversions/{id}
  • POST /v1/referrals/move
Use a REST API key from Settings → Developer & API for those.

Errors

See Errors and limits for every limit and what each error body carries.