Moov · Rate Limits

Moov Io Rate Limits

The Moov API enforces per-account request rate limits and returns HTTP 429 (Too Many Requests) when a client exceeds them. Moov does not publish specific numeric per-endpoint limits in its public reference; limits are applied per facilitator / account and may be raised for production platforms. Clients should honor 429 responses with exponential backoff. Webhook event delivery is separate: Moov considers a delivery failed if it does not receive a 2xx within 5 seconds and retries for up to 24 hours.

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

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

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

Tagged areas include Payments, Money Movement, Fintech, Rate Limiting, and Quotas.

3 Limits Throttle: 429
PaymentsMoney MovementFintechRate LimitingQuotasThrottling

Limits

API Requests account
requests
see provider documentation
Per-account request throttling on the REST API; exact rate is not published publicly.
Webhook Delivery Timeout endpoint
seconds
5
A webhook delivery is considered failed if your endpoint does not return a 2xx within 5 seconds.
Webhook Retry Window endpoint
hours
24
Failed webhook events are retried multiple times for up to 24 hours.

Policies

Backoff Strategy
On HTTP 429, implement exponential backoff with jitter before retrying.
Idempotency
Use idempotency keys on transfer creation to safely retry money-movement requests.
Webhook Reliability
Return a 2xx quickly and process events asynchronously; Moov retries for up to 24 hours on failure.

Sources