Omise · Rate Limits

Omise Rate Limits

Omise (Opn Payments) does not publish fixed numeric request-rate limits for its REST API in the public documentation. The API applies protective throttling and standard HTTP semantics; well-behaved integrations pace requests and handle retries idempotently. Pagination on list endpoints is bounded by a per-page limit (default 20, maximum 100) with offset, which effectively caps large-collection reads per request. Because charges move money, retries on create operations should be guarded to avoid duplicate charges rather than blindly retried.

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

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

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

Tagged areas include Payments, Payment Gateway, Thailand, Southeast Asia, and Rate Limiting.

2 Limits Throttle: 429
PaymentsPayment GatewayThailandSoutheast AsiaRate LimitingQuotas

Limits

API Requests account
requests
not published
No fixed numeric request-rate limit is documented; protective throttling may apply.
List Pagination request
records
100
List endpoints accept limit (default 20, max 100) plus offset.

Policies

Backoff Strategy
On HTTP 429 or 5xx, retry with exponential backoff and jitter.
Idempotency on Money Movement
Avoid blind retries of charge/transfer creation; verify state before retrying to prevent duplicate money movement.
Pagination
Page through large collections with limit and offset rather than requesting unbounded result sets.

Sources