Creem · Rate Limits

Creem Rate Limits

The Creem REST API returns HTTP 429 when a client exceeds its request rate. Specific per-account or per-endpoint request-per-minute thresholds are not published in the public documentation and are not reconciled in this artifact. Clients should implement retry-with-backoff handling for 429 responses.

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

It captures 1 rate-limit definition, measuring requests.

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

Tagged areas include Payments, Merchant of Record, Subscriptions, SaaS, and Billing.

1 Limits Throttle: 429
PaymentsMerchant of RecordSubscriptionsSaaSBillingRate LimitingQuotasThrottling

Limits

API Requests account
requests
see provider documentation
A 429 status is returned when the rate limit is exceeded; published numeric thresholds were not located.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor any Retry-After header.
Idempotency
Use the request_id field on checkout creation to safely retry without creating duplicate sessions.

Sources