Developer Documentation

REST API v1 (OAuth 2.0) — for integrations

The only credential /api/v1/* accepts. Create an app under API apps, copy the client ID and secret (the secret is shown once), then exchange them:

POST /api/oauth/token
Content-Type: application/json

{ "grant_type": "client_credentials",
  "client_id": "...", "client_secret": "..." }

-> { "access_token": "...", "token_type": "Bearer",
     "expires_in": 3600, "scope": "read write" }

Send it as Authorization: Bearer <access_token>. Scoped, revocable on its own, counted against the plan limits below, and refreshed by repeating the call. No human needed.

MCP (personal JWT) — for AI assistants

Business → Profile → API & Integrations → Copy Token. The JWT is copied to your clipboard.

Set Authorization: Bearer <token> on every MCP or REST Data API request. It does not authenticate /api/v1/*.

This is your own login, not a scoped key: it can write as well as read, it expires after an hour, and it is not counted by the usage meter. Treat it like a password.

What a JWT looks like: Three base64url segments separated by dots (header.payload.signature), typically 200–500+ characters. Example format:

eyJhbGciOiJIUzI1NiIs...eyJhdWQiLCJlbWFpbC...<signed>

Authorization: Bearer <your-jwt-token>
Content-Type: application/json