Booqable · Rate Limits

Booqable Rate Limits

The Booqable API applies request throttling and returns HTTP 429 Too Many Requests ("You're doing too many requests! Slow down!") when a client exceeds the allowed request rate. Booqable does not publish a fixed numeric requests-per-minute figure in its v4 developer documentation; the practical limit is enforced per account and observed in integrations (community reports describe GET call limits that require batching and back-off). Clients should implement exponential backoff on 429 responses and reduce request volume by using JSON:API includes to sideload related resources and pagination to fetch in pages rather than issuing many small requests.

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

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

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

Tagged areas include Rental Management, Inventory, Bookings, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Rental ManagementInventoryBookingsRate LimitingQuotas

Limits

API Requests account
requests
not published (429 on exceed)
Booqable throttles requests per account and returns 429 when exceeded. No fixed numeric rate is documented in the v4 API reference.
Pagination Page Size request
records
25 default per page
Collections are paginated via page[number] and page[size]; the default page size is 25 records.
Bulk Retrieval account
requests
use includes and pagination
High-volume reads should sideload related resources with include and page through results to stay under the throttle rather than issuing many single-resource requests.

Policies

Backoff Strategy
On a 429 response, back off and retry with exponential backoff and jitter, honoring any Retry-After header if present.
Efficient Fetching
Use JSON:API include to fetch related resources in one call and page[size] to control page size, reducing total request count.

Sources