A documented API with rate limits you can plan for
The developer API now has request and response documentation, pagination, scoped keys, and published rate limits.
An API is only useful if you can predict how it behaves. That means knowing the request shape, the response shape, and what happens when a client sends too many requests.
The developer API is now documented end to end.
What is documented
Every endpoint shows its request and response fields, including nested response objects. Certificate lists paginate instead of returning one unbounded result. API keys can be created with the scopes a workflow needs, given an expiry, and revoked when they should stop working.
Rate limits
Limits are published, so an integration can back off deliberately instead of discovering the ceiling in production. Most event teams start with CSV and move to the API when the same integration runs every cohort. Clear docs shorten that move; predictable limits keep a nightly sync from turning into an outage.
The API is a Pro feature. The docs are public, so you can evaluate the integration before upgrading.
Related