Quaderno · Rate Limits

Quaderno Rate Limits

Quaderno documents a fixed rate limit on its REST API: 100 requests per 15 seconds per account. Exceeding the limit returns HTTP 429 (Too Many Requests). Quaderno notes it may tune the limit but keeps it high enough for a well-behaving interactive app. The rate limit is separate from a plan's monthly transaction allowance, which meters billed documents rather than API calls. The /ping endpoint can be used to check availability and remaining allowance without consuming rate limit.

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

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

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

Tagged areas include Tax Compliance, Sales Tax, VAT, Invoicing, and Rate Limiting.

3 Limits Throttle: 429
Tax ComplianceSales TaxVATInvoicingRate LimitingQuotas

Limits

API Requests account
requests
100 per 15 seconds
Documented account-wide REST API rate limit; excess returns HTTP 429.
Ping account
requests
no rate-limit cost
The /ping endpoint checks availability and remaining allowance without consuming rate limit.
Monthly Transactions account
transactions
per plan
Not a request-rate limit - a billing allowance of processed documents per plan tier.

Policies

Throttling Response
Requests beyond 100 per 15 seconds receive HTTP 429 (Too Many Requests).
Backoff Strategy
Clients should implement exponential backoff with jitter and retry 429 responses after a short delay.
Server Error Retry
5xx responses (500, 502, 503, 504) are transient and should be retried later by the client.

Sources