Prelude · Rate Limits

Prelude So Rate Limits

Prelude does not publish fixed numeric per-endpoint rate limits in its public API reference. The API signals throttling with an HTTP 429 response (documented on the verification check endpoint). In practice, verification throughput is governed less by a request-per-second cap than by Prelude's own anti-fraud controls: create-verification can return statuses such as `blocked` or `shadow_blocked` and per-target retries are consolidated within a verification window rather than creating new verifications. Sustained volume and any account-level limits are handled through your plan and, on Enterprise, a 99.95% SLA.

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

It captures 3 rate-limit definitions, measuring requests, verifications, and feedbacks.

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

Tagged areas include Number Verification, OTP, Anti-Fraud, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Number VerificationOTPAnti-FraudRate LimitingQuotas

Limits

API Requests account
requests
not published
No fixed numeric request-rate limit is documented in the public API reference.
Verification Retries target
verifications
consolidated within the verification window
Repeated create calls for the same target within the window retry an existing verification instead of creating a new one.
Watch Feedback Batch request
feedbacks
100
The Watch feedback endpoint accepts up to 100 feedback items per request.

Policies

Anti-Fraud Gating
Create-verification may return blocked or shadow_blocked and per-target retries are windowed, acting as a fraud-oriented throttle rather than a fixed request cap.
Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 responses and honor any Retry-After header.

Sources