Skip to main content

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.

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

EndpointLimit
All endpoints (shared limit)100 requests / minute
note

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

EndpointLimit
GET /api/rules/schedule120 requests / minute

Transactions APIs

APIEndpointLimit
Transaction APIPOST /event/transaction/v3500 requests / second
Rule Rerun APIPOST /api/rules/rerun1 request / minute

Transactions Batch APIs

APIEndpointLimit
Transaction Batch APIPOST /api/transactions/batch/generate-upload-url20 requests / minute
Transaction Batch APIGET /api/transactions/batch/status/{batch_id}120 requests / minute
Transaction Batch APIGET /api/transactions/batch/validation-result/{batch_id}120 requests / minute
Rule Execution APIPOST /api/rules/execute30 requests / minute
Rule Execution APIGET /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.