Before you hire an API integration company in Dubai

Three quotes are on the desk. Each integration company has a portfolio of travel sites, each promises to "connect a flight API to your website", and the cheapest one can start next week. You run an agency in Deira with six staff and a steady corporate book, and you are tired of retyping fares from a supplier extranet into WhatsApp messages. Choosing the API integration company in Dubai that looks most competent feels like the whole decision.
It is about a third of it. The decisions that settle whether the site sells are not in any of the three quotes, because they are not code. They are who the supplier signed with, whose name the tickets are issued under, where the money sits between booking and ticketing, and who handles the refund when a customer cancels. An integrator can wire all of those together. It cannot be any of them for you.
This is written for the owner who will sign the statement of work, not for the developer who will read it.
What an API integration company in Dubai can deliver, and what it cannot
An integration company writes the code between a supplier's API and your website: the search form, the call that asks for availability, the price check before payment, the booking request, the screens that show the result and, if the scope says so, the calls that cancel and refund. The good ones also handle the dull parts that matter: retries when a supplier times out, logs that let a failed booking be traced, a test environment that behaves like production.
What it cannot hand you is everything on the far side of that code. Before a line is written, the agency needs:
- a supplier account in the agency's own name, with API access granted to that account;
- ticketing authority, either its own accreditation or a consolidator who issues on its behalf;
- a money arrangement with that supplier: a deposit, a credit line, or card payments passed through;
- someone who does the after-ticket work (voids, refunds, reissues, schedule changes), through the API or, failing that, by hand.
An integrator who offers to "sort out the supplier side" is usually offering to lend you theirs. As a shortcut for a prototype, that can be reasonable. For a business, it means your booking site runs on a relationship you do not hold and cannot take with you.
The brief: seven lines for the statement of work
Most disputes with an integrator trace back to a sentence nobody wrote down. Put these in the document you sign, in plain words, and ask for each answer in writing.
- Whose name is on the supplier account and the API keys. The agency's. Keys are credentials: they live in your password vault, and the integrator is given access, not ownership.
- Who hosts the site and who holds the domain. The domain is registered to the agency. The hosting account is the agency's, or the contract says exactly how it transfers.
- Which operations are in scope. List them by name: search, price, book, ticket, cancel, refund, change. Anything not on the list stays an email to the supplier's desk for the life of the site. Refunds and changes are the ones most often missing, because they are the ones a demo never shows.
- Who maintains it when the supplier changes its API. Suppliers retire versions and rename fields. A fixed-price build with no maintenance clause ends the day the first version changes.
- What handover means. Source code in a repository the agency owns, every credential, and a document that lets a different developer pick the work up. "We will send you a zip" is not a handover.
- How go-live is proven. A test booking from search to ticket in the supplier's test environment, including a cancellation, before anyone takes a real customer's card.
- What happens to customer data. Passenger names, passport details and payment references: where they are stored, who can read them, and how they are deleted.
None of these needs a technical background to write. Every one of them is cheaper to agree before the build than to negotiate after it.
Three ways to get supplier content onto your site
Hiring an integrator against a supplier's API is one route. It is worth seeing next to the other two before a quote makes the choice for you.
| Route | Who holds the supplier relationship | Who keeps the connection working | What the agency still builds | What leaving costs |
|---|---|---|---|---|
| Integrator connects your site to a supplier's API | The agency, if the brief says so; otherwise often the integrator | The integrator under a maintenance contract, or nobody | Admin, markups, customer records, reports, payments, servicing screens | Little if the code and keys are yours; a rebuild if they are not |
| Integrator connects your site to a platform's API | The platform holds supplier contracts; the agency holds its account with the platform | The platform for the supplier side; the integrator for your side | Your site, and whatever the platform's API does not cover | Rewriting your side against another API |
| White-label storefront that is already connected | The platform, through the agency's account | The platform | Content, pricing decisions, your own customers | Moving the domain and the customer list to another provider |
The row worth arguing about is the first. It gives the most control and puts the most on you: every supplier change, every new service and every operation the first build left out becomes another project with another quote.
How to put search on a site you already run is argued in adding flight search to an existing website, and choosing whose API stands behind it in what stands behind a flight booking API provider. This piece is about the contract around the work.
Where this platform sits
The platform behind this blog exposes flight and hotel APIs. Access starts as a conversation rather than a self-serve key, because the first questions are the ones above (which services, which market, how the money moves) rather than which endpoint to call. Services are activated per account, and every account has its own admin panel with its own bookings, customers, markups and reports, so the "still builds" column of the second row is shorter than it looks.
If an integration company is going to build your side, have that conversation before you accept a quote, so the scope describes the API it will really connect to. The travel APIs page is where it starts.
What a weak brief costs you
The site goes live. Search works, prices look right, and the first booking arrives on a Thursday evening. It cannot be ticketed in your name, because the supplier account belongs to the integrator and issues under their arrangement. The customer's card has already been charged. You now hold a booking you can neither ticket nor refund through your own site.
Or it works for a year. Then the supplier moves to a new API version, booking stops, and the integrator, whose fixed-price contract ended at handover, quotes for a new project. You pay it, because the only people who understand the code are the ones quoting.
Or the integrator is simply busy elsewhere. A customer needs a name corrected on a ticket, the change operation was never in scope, and two of your staff spend the afternoon emailing a supplier desk. That is exactly the work the site was meant to take away.
Each of these is one sentence that was missing from the brief. The code was fine every time.