Sequence · Rate Limits

Sequence Hq Rate Limits

Sequence publishes per-API-key rate limits on its REST API. Standard endpoints are limited to 1,500 requests per minute per API key. The high-volume usage ingestion endpoint (POST /api/usage-events) has a separate, much higher ceiling of 12,000 requests per minute per API key, reflecting its role as the metering hot path for usage-based billing. Requests over the limit are throttled with an HTTP 429 response.

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

It captures 2 rate-limit definitions, measuring requests.

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

Tagged areas include Billing, Usage-Based Billing, Metering, Rate Limiting, and Quotas.

2 Limits Throttle: 429
BillingUsage-Based BillingMeteringRate LimitingQuotas

Limits

Standard Endpoints api_key
requests
1500 per minute
Applies to standard REST endpoints (customers, billing schedules, invoices, products, quotes, etc.).
Usage Event Ingestion api_key
requests
12000 per minute
Higher dedicated ceiling for POST /api/usage-events, the metering ingestion path.

Policies

Per-Key Limits
Limits are enforced per API key (Client ID / Client Secret pair), so throughput can be scaled by provisioning additional keys where permitted.
Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 responses and honor any Retry-After header.
Idempotency
Usage events accept a customerEventId idempotency key so safe retries after throttling do not double-count usage.

Sources