API DOCUMENTATION / USAGE AND LIMITS
Usage and limits
Per-customer request limits, how returned records are counted, and how plans set your allowance.
Request windows are provisioned per customer
Customer policies can configure request windows and an optional monthly-record allowance. The policy schema can represent up to eight windows with durations from 1 second to 30 days, but those schema bounds are not the values assigned to a customer. The assigned account policy determines the applicable request limits.
Admission and record settlement are different
Authenticated requests are admitted before route input validation. An admitted malformed request can consume a request-window unit and settle zero records. Successful list/detail responses settle based on returned top-level data objects. Monthly records count successful settlements and can replace a would-be data response with 429 when a configured cap is exceeded.
Policies apply across keys for one customer
Request-window and monthly-usage queries group by customer ID, not API key or route class. If the service configures multiple keys for one customer, their admitted calls share those customer-level policy totals.
Unprovisioned shadow mode is not a free plan
Without an assigned policy, source usage can run in unprovisioned_shadow mode with no request windows or monthly cap. That implementation state does not define commercial terms or guarantee unmetered access.
How plans set your allowance
The pricing page lists each plan’s monthly job allowance; API requests on each plan are half its job count. Every job a response returns counts toward the monthly allowance, including a job you fetched before.
Continue in the reference
Check related request behavior before you build.
View route status and methods Discuss API requirements