Octobat · Rate Limits

Octobat Rate Limits

Octobat does not publish fixed numeric rate limits for its REST API (https://apiv2.octobat.com) in its public documentation. As a Stripe-style billing API it is expected to apply per-account request throttling and to return HTTP 429 (Too Many Requests) when limits are exceeded; clients should implement exponential backoff with jitter. Test-mode (sk_test_) and live-mode (sk_live_) keys are metered separately. Practical throughput is also bounded by each account's plan-level invoice / transaction volume allowance rather than by a documented per-minute request cap.

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

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

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

Tagged areas include Billing, Invoicing, Tax Compliance, Rate Limiting, and Quotas.

3 Limits Throttle: 429
BillingInvoicingTax ComplianceRate LimitingQuotas

Limits

API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the apiv2.octobat.com API.
Document Volume account
documents
per plan
Invoice / credit-note / transaction throughput is governed by the account's subscription tier allowance.
Test vs Live key
requests
separate per mode
Test-mode and live-mode secret keys are throttled and metered independently.

Policies

Backoff Strategy
On HTTP 429, implement exponential backoff with jitter and honor any Retry-After header before retrying.
Idempotency
Follow Stripe-style safe-retry practices for create requests to avoid duplicate invoices or transactions on retry.
Environment Separation
Use sk_test_ keys for development and sk_live_ keys for production; the two environments are isolated.

Sources