Every production on the platform lives on one set of records: projects, documents, money, people. The API reads and writes those same records, scoped to exactly what you grant it.
Three domains are open to third parties now. Everything below ships in the spec and runs in production.
29 document types with a machine-readable contract each: JSON Schema, sample data, and merge-field paths. Post your data or a record id and get rendered HTML back.
GET /api/v1/documentsA catalog of 77 KPI definitions and 43 reports, computed live from the caller's org data. Metrics without backing data return null.
GET /api/v1/metricsRead a project's advance packet graph or create the packet shell, and track a merge send's per-recipient delivery funnel. Portal tokens never leave the platform.
GET /api/v1/projects/{id}/advance-packetsPersonal access tokens carry named scopes. A reporting integration gets reports:read and nothing else. These are the scopes open to third parties today.
| Scope | What it grants |
|---|---|
documents:read | List document types and read each type's JSON Schema, sample, and merge-field paths. |
documents:write | Generate documents from your own data or from a record you can access. |
reports:read | Read the metric catalog, resolve metric values, and pull reports and snapshots. |
advancing:read | Read advance packets, sections, audiences, and send-batch tracking boards. |
advancing:write | Create a project's advance packet shell (manager role or above). |
Stripe is wired into the platform natively: checkout, Connect onboarding, and signature-verified webhook receipt. You don't build payment plumbing to integrate with us.
Built something on the API? Submit it for review and we'll list it in the integrations directory where operators go looking.
Agencies and implementation shops get a public profile in the live agency directory and a direct line to the team.
Read it, mint a token, and make your first call this afternoon. When it works, list it.