Retry-After header.
How limits work
Each limit has two numbers: a sustained rate and a burst.- Sustained rate. The steady number of requests you can send per minute. Allowance refills continuously, not at the top of each minute: a limit of N per minute gives you one more request every 60 ÷ N seconds.
- Burst. How many requests can arrive at once when you haven’t used any allowance. After a burst, the allowance refills at the sustained rate, one request at a time.
Finding and raising your organization’s limits
To find out your organization’s limits, or to raise them for an integration that sends many requests, such as batch pricing, contact Pylon support. You can also read the current sustained rate for any call from theX-RateLimit-Limit header on its response.
Pricing limits
Pricing operations (scenario pricing, loan product pricing, optimal structure, marketing rates and prequalification) have a lower limit than the rest of the API. Most other calls are unlikely to reach theirs. A GraphQL request that asks for several pricing fields at once counts once for each field.Recognizing a limited request
How a limited request looks depends on the API you call.GraphQL
A limited GraphQL request returns HTTP 200, like every GraphQL response. The limited field comes back asnull with an error whose extensions.code is RATE_LIMITED:
extensions.code, not the HTTP status or the message text.
REST
A limited REST request returns HTTP 429 with"code": "RATE_LIMITED" in the body. See MISMO import for an example.
Rate limit headers
Responses to authenticated requests carry these headers, for both GraphQL and REST.401 and 403 responses don’t carry them.
The headers describe the limit that applied to the request. A GraphQL request that touches pricing reports the pricing limit.
Retrying a limited request
Wait for the number of seconds inRetry-After, add a little random jitter, then send the same request again. Treat it as unfinished until it succeeds.
Sending batches
If you price or update many records at once, pace your requests to the sustained rate rather than relying on retries. To stay under the limit with batches, start each batch no sooner than the batch size multiplied by the time between requests. Take the sustained rate fromX-RateLimit-Limit:
X-RateLimit-Remaining. When it gets close to zero, pause until enough allowance has refilled.