Overview
Rate limits vary by endpoint and account. When a limit is exceeded, the API returns HTTP 429 with aRetry-After header (seconds).
Meum may apply different limits to authentication, checkout, invoice creation, integrations, and dashboard operations. Exact thresholds are not published as a fixed contract while limits are being calibrated on some routes.
Rate limit response
When a limit is enforced:Integration guidance
- Retry idempotent reads with exponential backoff when you receive 429.
- Use
Idempotency-Keyon dashboard payment link creation where supported. - WooCommerce invoice creation is deduplicated by
external_order_idper store. Retries with the same order ID return the existing invoice when possible. - If multiple integrations share one egress IP, coordinate request volume; per-API-key accounting may apply on some routes.
Related pages
- Common API errors
- Idempotency (if documented)