Invoiced · Rate Limits

Invoiced Rate Limits

The Invoiced REST API applies per-account rate limiting to protect platform stability. Specific request-per-second / per-minute thresholds are not published in the public API reference and vary by account. Clients should watch for HTTP 429 responses and back off accordingly. List endpoints are paginated via page and per_page (max 100 per page), which serves as a practical throughput control. Specific numeric limits are not reconciled in this artifact.

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

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

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

Tagged areas include Accounts Receivable, Billing, Payments, Subscriptions, and Rate Limiting.

2 Limits Throttle: 429
Accounts ReceivableBillingPaymentsSubscriptionsRate LimitingQuotasThrottling

Limits

Per-Account Request Rate account
requests
see provider documentation
Per-API-key request throttling; specific thresholds are not published.
List Pagination request
records
100
Maximum records per page on list endpoints via per_page; default 25.

Policies

Backoff Strategy
On HTTP 429, clients should retry with exponential backoff and jitter.
Pagination
Use page and per_page to traverse large result sets rather than large single requests.
Sandbox Testing
Use https://api.sandbox.invoiced.com to test integrations without affecting production limits or data.

Sources