API Rate Limits
Transaction Monitoring APIs apply per-tenant rate limits, in line with Fenergo's platform-wide approach to API Rate Limits. Rate limits protect the stability of the service for all tenants by capping how many requests a single tenant can send to a given endpoint in a given time window.
The rate limits described on this page apply only to requests authenticated through CLM (the Fenergo SaaS API Gateway). Requests using other authentication methods are not subject to these rate limits. See the TM API Proxy URL Update release note for how authentication through CLM works for Transaction Monitoring.
Limits by endpoint
Limits apply per tenant, per endpoint. Calling an endpoint from multiple integrations or applications under the same tenant shares the same limit.
Observability API
| Endpoint | Limit |
|---|---|
| All endpoints (shared limit) | 100 requests / minute |
This limit is shared across all of the Observability API's endpoints (transaction summary, batch status, rule execution, data export, etc.) rather than applied separately to each one.
Rule Schedule API
| Endpoint | Limit |
|---|---|
GET /api/rules/schedule | 120 requests / minute |
Transactions APIs
| API | Endpoint | Limit |
|---|---|---|
| Transaction API | POST /event/transaction/v3 | 500 requests / second |
| Rule Rerun API | POST /api/rules/rerun | 1 request / minute |
Transactions Batch APIs
| API | Endpoint | Limit |
|---|---|---|
| Transaction Batch API | POST /api/transactions/batch/generate-upload-url | 20 requests / minute |
| Transaction Batch API | GET /api/transactions/batch/status/{batch_id} | 120 requests / minute |
| Transaction Batch API | GET /api/transactions/batch/validation-result/{batch_id} | 120 requests / minute |
| Rule Execution API | POST /api/rules/execute | 30 requests / minute |
| Rule Execution API | GET /api/rules/status/{execution_id} | 120 requests / minute |
What happens when you exceed a limit
A request over the limit receives an HTTP 429 Too Many Requests response with a Retry-After header indicating how many seconds to wait before retrying.
HTTP/1.1 429 Too Many Requests
Retry-After: 42
Designing for rate limits
See Designing for Rate Limits for recommended integration patterns, including retry-with-backoff and caching your authentication token.
Requesting a higher limit
If your integration has a legitimate need for a higher limit on a specific endpoint, work with your Client Partner or Solution Architect to discuss options.