Build on the platform your customers already run their business on.
A REST API with one token, one word for a sub-account, and refusals that name their own cause. 27 operations, 14 scopes, and a reference generated from the router itself — so it cannot describe an endpoint that does not exist.
No account needed to read any of this. You only need one to get a key.
Four steps, and there is no fifth
- 1Get a key
Settings → API keys. Usable immediately, no review queue.
- 2Call an endpoint
One header. The same key reaches every sub-account you own.
- 3Subscribe to events
Webhooks, so you stop polling.
- 4Ship it
Register an OAuth app to act on other people's accounts.
What you can build
Read and write contacts, opportunities, calendars and conversations with a key you make in Settings.
OAuth with PKCE, refresh rotation, and scopes the customer sees before approving.
You host it, we frame it, and it never holds a credential that outlives the visit.
Signed webhooks with retries over three days, a delivery log, and a resend button.