Quandoo · Rate Limits

Quandoo Rate Limits

The Quandoo Public Partner API is gated by a partner authentication token (X-Quandoo-AuthToken) and scoped per partner agreement. Quandoo's public documentation does not publish explicit numeric request-rate or concurrency limits for the Partner API; integrations are validated first against the test environment (test-9250-api.quandoo.com) before being promoted to production (api.quandoo.com / public-api.prod.quandoo.com). The most consumer-actionable controls are the idempotency requirements on reservation and enquiry creation and the conflict semantics on no-longer-bookable slots, rather than published per-second quotas. Numeric limits below are left as descriptive strings and reconciled is false because Quandoo does not document hard rate-limit numbers publicly.

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

It captures 2 rate-limit definitions, measuring varies.

The profile also includes 4 backoff/retry policies defined and response codes documented for badRequest and conflict.

Tagged areas include Rate Limiting, Reservations, and Marketplace.

2 Limits
Rate LimitingReservationsMarketplace

Limits

Partner API requests (production) token
varies
not publicly documented; governed by partner agreement / Partner Service Level
Partner API requests (test environment) token
varies
not publicly documented; test environment must be used before production
Test bookings must only be made on test-9250-api.quandoo.com; live bookings only on production.

Policies

Idempotent reservation creation
Reservation creation (PUT /v1/reservations) and reservation-enquiry creation (PUT /v1/reservation-enquiries) are idempotent. The client must supply an agent-specific unique ID; resubmitting the same request does not create a duplicate reservation.
Booking conflict handling
If the requested reservation option is no longer bookable, the API returns HTTP 409. Clients should re-check availability and surface the conflict rather than blindly retrying.
Validation failures
Missing or malformed required parameters return HTTP 400. Validate input (including phone numbers via GET /v1/validations/phone-numbers) before submitting a reservation.
Environment promotion
All integration and testing must run against the test environment first; only verified integrations are enabled on production, and no test bookings may be made against production.

Sources