Payhip · Rate Limits

Payhip Rate Limits

Payhip does not publish numeric rate limits for its public REST API (Coupons and License Keys). Standard HTTP status codes apply, and callers should assume an unspecified fair-use ceiling and implement retry/backoff on errors. For outbound webhooks, Payhip documents a concrete delivery-retry policy: the receiving endpoint must return HTTP 200, and failed deliveries are retried hourly for up to three hours before being dropped.

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

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

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

Tagged areas include E-commerce, Coupons, License Keys, Webhooks, and Rate Limiting.

2 Limits Throttle: 429
E-commerceCouponsLicense KeysWebhooksRate Limiting

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the Coupons or License Keys endpoints.
Webhook Delivery Retries endpoint
deliveries
hourly retry for up to 3 hours
Failed webhook deliveries (non-200 responses) are retried hourly for up to three hours, then dropped.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 or 5xx responses from the REST API.
Webhook Acknowledgement
A webhook receiver must respond with HTTP 200 to acknowledge delivery; otherwise Payhip retries the event hourly for up to three hours.
Signature Verification
Verify each webhook by comparing its signature field with hash('sha256', apiKey) before trusting the payload.

Sources