RecVue · Rate Limits

Recvue Rate Limits

RecVue does not publish fixed numeric API rate limits in its public developer reference. As an enterprise platform, throughput and any per-tenant limits are governed by the customer's agreement and tenant sizing rather than a public per-minute request cap. For high-volume work RecVue directs clients to the Bulk API (asynchronous CSV import of up to 10,000 orders per job, plus bulk price-list and tier imports) and to asynchronous concurrent programs (bill runs, revenue recognition, exports) and a Spark-based rebill path for 10,000+ schedules, rather than to high-frequency synchronous calls.

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

It captures 4 rate-limit definitions, measuring requests, orders, schedules, and jobs.

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

Tagged areas include Revenue Recognition, Billing, Revenue Management, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Revenue RecognitionBillingRevenue ManagementRate LimitingQuotas

Limits

Synchronous API Requests tenant
requests
not published
No fixed numeric request-rate limit is documented in the public reference.
Bulk Order Import job
orders
10000 per import job
Asynchronous CSV import; use for large order loads instead of per-order POSTs.
Rebill Spark Program job
schedules
designed for 10000+ schedules
Parallel processing path for large rebill batches.
Concurrent Programs tenant
jobs
async
Bill runs, revenue recognition, tax, and exports run asynchronously via program execution.

Policies

Prefer Bulk and Async
Large data operations should use the Bulk API and concurrent-program execution rather than high-frequency synchronous calls.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources