🔌 Public API introduction
Scoped keys, rate limits, and what you can build against the /v1 surface.
Keys and scopes
Owners can issue API keys with explicit scopes — a key only reaches the resources its scopes name, and each key carries its own rate limit (default 120 requests/minute). Keys are shown once at creation; store them like passwords.
What the API covers
The /v1 REST surface covers core business objects — leads, jobs, invoices and account data — always scoped to your business. The self-describing OpenAPI document is available inside the app (Developer section), generated from the running API rather than hand-maintained.
Good practices
- One key per integration, minimum scopes each.
- Handle 429 responses by backing off — limits are per key, per minute.
- Rotate keys when staff or vendors change.
Still stuck?
Support and the contact form reach a human.