Duffel · Rate Limits

Duffel Rate Limits

The Duffel API applies per-endpoint rate limits and returns HTTP 429 with a rate_limit_exceeded error when they are exceeded. Responses expose RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers describing the window. Limits vary by endpoint and account; in addition, a commercial search-to-book ratio (1500:1) governs how many searches are included before excess search fees apply. Specific per-endpoint numeric limits are not reconciled in this artifact.

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

It captures 2 rate-limit definitions, measuring requests and searches_per_order.

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

Tagged areas include Travel, Flights, Hotels, Booking, and Payments.

2 Limits Throttle: 429
TravelFlightsHotelsBookingPaymentsRate LimitingQuotasThrottling

Limits

Per-Endpoint Request Limit account
requests
see provider documentation
Limits vary by endpoint; reported via RateLimit-Limit / RateLimit-Remaining / RateLimit-Reset headers.
Search-to-Book Ratio account
searches_per_order
90001
Commercial ratio; searches beyond 1500 per confirmed order incur a $0.005 per-search excess fee.

Policies

Rate Limit Headers
Clients should read RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset to pace requests.
Backoff Strategy
On HTTP 429, implement exponential backoff with jitter and retry after the reset window.

Sources