Reliability you can check
Travel sites change, slow down and push back. Here is what the API does about it, and how you can check it yourself before you depend on it.
- Failed calls cost 0 credits
- Public status page
- Public OpenAPI spec
What the API does on every call
Six things you can rely on, each one something you can verify.
A public status page
The website, the API and sign-in are checked every 60 seconds, with history anyone can read on the public status page.
Open the status pageHourly checks on the routes you use
Every hour, live checks call the routes customers rely on most against the real sites.
Self-repair when a site changes
When a site changes its pages, extraction falls back to other paths and checks the result before it is returned.
Blocking and retries are our problem
Sessions, blocking, parsing and retries are handled on our side.
Failed calls cost nothing
A 4xx or 5xx response or an empty page costs 0 credits, and every response reports what it charged in x-credits-charged.
How credits workEvery call can be traced
Every request, and the response it returned, can be opened in your dashboard.
Read about request history
A failed call, as your code sees it
Errors are explicit and free. Retry 429, 502 and 503 with backoff; nothing is charged until a call succeeds.
HTTP/1.1 502 Bad Gateway
x-credits-charged: 0Reliability questions
What happens when a source site is down or refuses a request?
The call returns an error (502 when the upstream site failed or returned an unusable answer) and costs 0 credits. 429, 502 and 503 responses are safe to retry with backoff.
How do I know whether the API is having a problem right now?
The website, the API and sign-in are checked every 60 seconds, with history anyone can read on the public status page. It runs on its own hostname, so it stays up when this site is down.
What happens when a site redesigns its pages?
When a site changes its pages, extraction falls back to other paths and checks the result before it is returned. The response keeps its documented shape, so your parser does not change.
Do I pay for retries?
Only for the call that succeeds. Failed or blocked calls, any 4xx or 5xx response, and empty search pages cost 0 credits.
Can I see exactly what a call returned?
Every request, and the response it returned, can be opened in your dashboard. The API also returns x-credits-charged on every response, so your own logs show what each call cost.
Start with 50 free calls
Create an account and verify your email: your own API keys and a free trial of 50 calls or 14 days, whichever ends first, no card needed. Then buy a credit pack from $15 or pick a plan from $49 a month.
7,500 credits, one-time. No subscription. Or try it free: 50 calls, no card.