Developer API
Last updated September 23, 2026
Search our flights, link travellers straight into a booking, and earn commission on what you send. Everything below is served from https://aviodeals.com.
Already a partner? Your statistics, bookings and monthly statements are in the partner portal. Partner sign-in
Getting access
The affiliate programme is open: anyone can join. Fill in the form below and we email you a link to your trial credentials straight away. Tell us about your project at the same time; that is what we base a commercial agreement on.
- A tracking code — the value you put in the ref parameter on every link you send us.
- An API token for the search and feed endpoints.
- Commission terms: a percentage of the order total, up to an agreed maximum per booking.
Your token is a bearer credential: anyone holding it can query as you. We store only a hash of it, so we cannot read it back to you — keep it somewhere safe, and tell us straight away if it leaks and we will replace it.
A trial account is limited, so that evaluating us never costs an airline contract:
- It ends after 30 days unless we have agreed terms by then.
- Up to 500 search requests a day.
- Searches are answered from our price store, which our own customers and live partners keep filled. A route and date nobody has searched recently may answer empty; production accounts trigger live refreshes.
- Bookings you send during the trial are tracked to your code. Commission is paid from the date of your agreement.
Get trial credentials
Authentication
Send your token on every feed and search request, either as an Authorization header carrying the raw token — with no Bearer prefix — or as an accessToken query parameter. The redirect endpoints are public and take no token.
Example
curl -H "Authorization: YOUR_TOKEN" \
"https://aviodeals.com/api/v2/data/routes.json"Failures
Both answer HTTP 401 with the code ERROR_UNAUTHORIZED:
- No token at all: Authentication required
- A token we do not recognise, or one belonging to a deactivated account: Access Denied [1]
Endpoints
Responses are JSON. Dates are ISO 8601 (YYYY-MM-DD). Airports are referenced either by IATA code or by the numeric id from the airports feed; both are accepted everywhere an airport is named.
Baggage and fare options are only ever returned by the two addresses ending in -tcs: flights-tcs.json and flights-multi-tcs. The other addresses never change, so an integration built on them keeps working exactly as it does today.