Forter · Rate Limits

Forter Rate Limits

Forter does not publish fixed numeric rate limits for its Decision API in the public documentation. The API is a real-time, synchronous decision service called inline at checkout, signup, and login; throughput is provisioned per account to match the merchant's transaction volume rather than governed by a published per-minute request cap. Practical limits, timeouts, and failover behavior (for example, how to handle a timeout or a non-2xx response at checkout) are defined per integration during onboarding.

Forter Rate Limits is the machine-readable rate-limit profile for Forter on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests and milliseconds.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Fraud Prevention, Payments, E-commerce, Rate Limiting, and Quotas.

2 Limits Throttle: 429
Fraud PreventionPaymentsE-commerceRate LimitingQuotas

Limits

Decision API Requests account
requests
not published
Provisioned per account to match transaction volume; no public numeric cap.
Real-Time Decision Latency request
milliseconds
synchronous / inline
Called inline at checkout, signup, and login; integrations define timeout and fallback handling.

Policies

Provisioned Throughput
Capacity is sized per account during onboarding rather than exposed as a public rate limit.
Backoff Strategy
Clients should implement retries with exponential backoff and jitter and honor Retry-After on 429 responses.
Failover Handling
Define fail-open or fail-closed behavior for checkout when a decision call times out or errors, per Forter integration guidance.

Sources