KOMOJU · Rate Limits

Komoju Rate Limits

KOMOJU does not publish fixed numeric rate limits for its REST API (https://komoju.com/api/v1) in its public documentation. As a production payment gateway it applies standard abuse and fraud protections, and clients should be prepared to handle HTTP 429 (Too Many Requests) with backoff. KOMOJU does document request-safety mechanisms that interact with retries: POST requests support idempotency via the X-KOMOJU-IDEMPOTENCY header (keys valid up to 24 hours), and a request retried before its initial response has been produced returns HTTP 409.

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

It captures 3 rate-limit definitions, measuring requests, hours, and characters.

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

Tagged areas include Payments, Payment Gateway, Japan, Rate Limiting, and Quotas.

3 Limits Throttle: 429
PaymentsPayment GatewayJapanRate LimitingQuotas

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the KOMOJU REST API.
Idempotency Key Validity request
hours
24
X-KOMOJU-IDEMPOTENCY keys are valid up to 24 hours after first use, then become reusable.
Idempotency Key Length request
characters
100
Idempotency keys are limited to 100 ASCII characters.

Policies

Idempotent Requests
POST requests accept an X-KOMOJU-IDEMPOTENCY header so retries execute the operation at most once; the original response is replayed for repeated keys.
In-Flight Retry Conflict
Retrying a request with the same idempotency key before the initial request has produced a response returns HTTP 409.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 responses.

Sources