Rate Limits
The Oracle Access Governance REST API enforces rate limits to maintain system performance. Each Service Instance is assigned its own per-minute request limits for API operations. Refer the rate limits defined in the following table.
Table - Rate Limit Overview
| Operation Type | Per Minute Limit | Description |
|---|---|---|
| Read-only Operations | 180 requests |
Default limit for read-only operations (e.g., GET requests) |
| Write Operations | 60 requests |
Limit for operations that modify the system (e.g., POST (with exceptions), PUT, DELETE requests). |
Rate Limit Behavior
- Limit Exceeded Response: When the request limit is reached, subsequent API calls will receive a 429 Too Many Requests HTTP response
- Response Headers: The API uses response headers to provide rate limit information to the caller.
| Header Name | Description | Example Value |
|---|---|---|
RequestLimit-Default-Remaining |
Indicates how many read-only requests remain before reaching the
limit. The Remaining headers are present in all
responses, regardless of the HTTP status code.
|
179 |
RequestLimit-Write-Remaining |
Indicates how many write requests remain before reaching the
limit. The Remaining headers are present in all
responses, regardless of the HTTP status code.
|
59 |
RequestLimit-Default-RetryAfter |
(On 429 response) Indicates milliseconds until the read-only limit resets. | 30000 (30 seconds) |
RequestLimit-Write-RetryAfter |
(On 429 response) Indicates milliseconds until the write limit resets. | 30000 (30 seconds) |