Rate Limiting
Usage of the Oracle Textura Payment Management Public API is subject to rate limits. By limiting the number of API requests that can be issued from a unique user, we are able to offer a more reliable service.
Textura Cloud Rate Limits
The Oracle Textura Payment Management API has a maximum rate limit of 25 requests per second per user IP address. The maximum rate limit may extend up to 65 requests per second in some cases. The rate limit resets every second of public API's server time.
When the user exceeds the invocation rate beyond the maximum rate limit for a current second, the client will receive a 429 HTTP response status code. The response body will contain the following message.
Response |
|---|
|
Tips For Working Within the Maximum Rate Limit
The following tips will help you to code defensively and reduce the possibility of exceeding the rate limit.
- Cache results whenever possible. This is especially true when you are displaying data to the public.
- Use logging to see how many requests you are making and throttle them as per the Oracle Textura Payment Management API rate limit.
Last Published Friday, September 5, 2025