Telr · Rate Limits

Telr Rate Limits

Telr does not publish explicit numeric per-second/per-minute rate limits for its gateway (order.json / remote.json) or REST (/api/v1) endpoints. Access is governed instead by per-store Service API keys, which can be scoped to specific services and restricted to a set of publicly-routable IP addresses (comma-separated allow-list). Abuse controls, anti-fraud/risk screening, and duplicate-transaction protection (unique cart id enforcement, e.g. error "E56:Duplicate transaction") act as the practical throttles rather than a documented request-rate quota.

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

It captures 4 rate-limit definitions, measuring requests, source_ips, cart_id, and endpoints.

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

Tagged areas include Payments, Payment Gateway, MENA, UAE, and Rate Limiting.

4 Limits
PaymentsPayment GatewayMENAUAERate LimitingQuotas

Limits

Request Rate store
requests
not published
No numeric RPM/RPS limit is documented; governed by anti-fraud/risk controls.
IP Allow-list api_key
source_ips
configurable
Service API keys can restrict access to specific publicly-routable IP addresses (comma-separated). Private/internal IPs are not accepted.
Duplicate Transaction Protection store
cart_id
unique per order
Cart id must be unique per order; duplicates are rejected (e.g. E56).
Webhooks order
endpoints
2
The REST Payments API accepts up to two webhook URLs per order.

Policies

Key Scoping
API keys are scoped to permitted services and IP ranges in Merchant Administration.
Backoff Strategy
Clients should retry idempotently on transient failures using a fresh unique cart id only when the prior order is confirmed not created.

Sources