Skip to main content
In your Partner platforms → Developers workspace, generate a managed API key and register a signed webhook endpoint for your platform. An Already admin can also manage these connections in Admin → Connections. Each key and webhook signing secret is shown once on creation; the API stores a hash of the API key for authentication. Send the key from your server on every partner API request:
Use the fewest scopes your integration needs. A key is tied to its partner, so changing an ID in a request does not grant access to another partner’s records. Rotate or revoke keys in Developers when access changes; the old key stops working immediately after rotation.

Rate limits and browser origins

The current default is 60 requests per minute per API client. Admin can set a lower or higher value, capped by the service at 600 per minute. Counters are stored in the shared API database. Responses include X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset; HTTP 429 includes Retry-After. Allowed browser origins can restrict requests that carry an Origin header. They are not authentication: server requests normally have no browser origin, and every request still needs the bearer key. Keep API keys out of web apps, mobile bundles, iframe URLs, and client logs. Connections also displays request successes and errors, webhook delivery attempts, and endpoint status. A test event confirms delivery but does not validate a full invoice workflow.