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, in the API Commons Rate Limits shape.
It captures 2 rate-limit definitions, measuring requests and records.
An exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
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.
generated, dated 2026-07-12.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.