Flight Centre is an Australian-headquartered retail travel agency group trading across Australia, New Zealand, Canada, South Africa and the United Kingdom. It sells flights, accommodation, holiday packages, tours, cruises, car hire and rail through retail stores, phone consultants and its own apps, with a World360 Rewards loyalty program. For operators, it brings agent-advised leisure travelers, led by Australians and New Zealanders, who book attractions and tours as part of a long-haul package arranged weeks or months before departure, so demand is long-lead and often tied to multi-city itineraries. Flight Centre uses Cobber as their connectivity provider.

Connecting Flight Centre to Ventrata syncs your availability and prices and delivers bookings, changes and cancellations with tickets issued automatically. Flight Centre runs on Cobber, and receives your products through its certified integration with Ventrata's OCTO API.

To learn more about partnering with Flight Centre, visit flightcentre.com.

Primary website	flightcentre.com
Tags	Travel Agent · Offline & Retail Channel
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Agent-booked long-haul holiday packages
Connection features	Availability Sync · Pricing Sync · Bookings Sync · Pickups/Dropoff Sync
Ventrata Booked GMV (last 12 months)	US$1M+
Ventrata Booked Suppliers (last 12 months)	10+
Developed by	Cobber (formerly Respax & Livn) (using Ventrata's OCTO API)

This reseller connection lets you sell your products through Flight Centre without managing availability, pricing and bookings by hand. Features of this connection include:

Availability Sync – Flight Centre checks your live availability in Ventrata.
Pricing Sync – Flight Centre gets your prices from your reseller pricing in Ventrata.
Bookings Sync – bookings, updates and cancellations from Flight Centre are created in Ventrata instantly, and customers get Ventrata tickets.
Pickups/Dropoff Sync – pickup and dropoff details on Flight Centre bookings are passed to Ventrata.

Creating the Flight Centre Connection

🔐 Required Role Permissions: See Connections, Modify Connections, See Connection Key

Before you begin:

You must have a commercial agreement with Flight Centre for them to sell your products. To inquire about partnering with them, contact them via flightcentre.com.
You must have Flight Centre created as a Reseller in Ventrata with their pricing (retail, wholesale/commission) defined correctly. Note that this API connection requires that the reseller is set to the "Bill to my account" settlement method.

In Ventrata Dashboard, go to Connections → Connections, click + New Connection, and select Flight Centre (powered by Cobber) from the list of partners.
Select Flight Centre Reseller from the list of your resellers (must be created before creating a connection). The connection will inherit the reseller's configuration like pricing, allowed destinations, products, etc.
(Optional) You can also set the connection Name of your choosing, which may be helpful if you plan to have multiple Flight Centre connections and would like to differentiate between them more easily in the future.
Press the Create Octo Connection button.

📗 TIP

If needed, you can also allow or disallow products or destinations on the connection level, in addition to what you have configured on the reseller.

Mapping Products to Flight Centre

Securely share the OCTO API key shown on the connection you've created with your Flight Centre contact and ask them to map your products using Ventrata's OCTO API, with pricing (octo/pricing) enabled. Typically, it takes no longer than a few business days for the Flight Centre team to complete this.

Your Ventrata configuration is complete. You do not need to take any further steps.

📗 TIP

Flight Centre can access all products enabled on the connection, but you can also provide the Product and Option IDs from the connection page when contacting them to specify what to map.

Managing the Flight Centre Connection

Allow or disallow products: limit which destinations, products and options Flight Centre can access. See how to allow or disallow products.
Rename the connection to tell several Flight Centre connections apart.

Connection Features Detailed

This section is for anyone who wants to know exactly how the Flight Centre connection works: which Ventrata OCTO API calls Flight Centre makes (through Cobber's certified integration), when it makes them, and what that means for you. Each call links to Ventrata's API documentation.

In short: Flight Centre pulls everything it needs from Ventrata. It reads your products, checks your availability and prices, and sends bookings and cancellations. Ventrata doesn't push changes to Flight Centre, so anything you change in Ventrata reaches Flight Centre the next time it checks.

Timings are typical for Flight Centre and rounded, and they can change if Flight Centre changes how it syncs.

Product Mapping	❌	You can't map products from Ventrata. Flight Centre maps them on its side, through your account manager or Flight Centre's portal. This works as follows: Get Products (`GET /products`) – when Flight Centre sets up your connection, and whenever it refreshes its listings, it reads every product enabled on the connection, with its options and units (ticket types such as Adult or Child). Get Product (`GET /products/{productId}`) – Flight Centre re-reads a single product to pick up changes to its options, units, booking cutoffs and settings. Mapping on Flight Centre's side – Flight Centre links each Ventrata option and unit to its own listing and ticket types. Your Flight Centre account manager does this for you, or you do it in Flight Centre's own portal if Flight Centre offers one. You only share the connection's API key. Typically with Flight Centre: Flight Centre reads your full product list about once a day. It re-reads each product about every 7 hours. What this means for you: Flight Centre can only sell what it has mapped. When you add a product, option or unit in Ventrata, Flight Centre may see it on its next refresh, but it won't sell it until it's mapped. So tell your Flight Centre account manager whenever you add one.
Content Sync	✅ / ❌	Flight Centre can read your product content, such as descriptions and images, from Ventrata. This works as follows: `octo/content` capability – when Flight Centre adds it to the `Octo-Capabilities` header, Get Products (`GET /products`) and Get Product (`GET /products/{productId}`) also return your product content, such as descriptions, highlights, inclusions and images. Content changes in Ventrata reach Flight Centre on its next product refresh. Typically with Flight Centre: Flight Centre requests `octo/content`.
Availability Sync	✅	Flight Centre checks your live availability in Ventrata. Ventrata doesn't push availability changes to Flight Centre. This works as follows: Availability Check (`POST /availability`) – Flight Centre sends a product, an option and a date or date range. Ventrata answers with each bookable day or time slot, its status (`AVAILABLE`, `LIMITED`, `SOLD_OUT`, `CLOSED` or `FREESALE`), the remaining vacancies, the booking cutoff and an `availabilityId`, which Flight Centre needs to book that slot. Availability Calendar (`POST /availability/calendar`) – returns one summary per day instead of every time slot, typically to show which dates are open in a date picker. Check at booking – when a customer books, Ventrata checks capacity again before it creates the booking, so Flight Centre can't overbook a slot that has just sold out, even if its stored availability is slightly out of date. Typically with Flight Centre: Availability Check: Flight Centre checks your products throughout the day, usually starting about 5 months ahead and covering a single day per request, looks up to about a year ahead and re-checks the same product and dates about every 10 hours. Availability Calendar: Flight Centre checks your products throughout the day, usually starting 4 days ahead and covering a single day per request, looks up to about a year ahead and re-checks the same product and dates about every 9 hours. Checks are busiest between 00:00 and 06:00 UTC, which suggests most checks are live, as customers browse Flight Centre. What this means for you: when you close a date, change capacity or sell out in Ventrata, Flight Centre shows it after its next check. For dates it checks regularly, that's within about 9 hours. Dates further ahead are usually checked less often.
Pricing Sync	✅	Your prices come back with every availability check, once Flight Centre asks for them with the octo/pricing capability. This works as follows: `octo/pricing` capability – Flight Centre asks for prices by adding `octo/pricing` to the `Octo-Capabilities` header of its requests. Without it, Ventrata sends availability with no prices at all. Availability Check (`POST /availability`) – with pricing on, each day or time slot comes back with your price per unit (ticket type): the retail price the customer pays and the net price you invoice Flight Centre, both from the reseller's pricing in Ventrata (retail and wholesale/commission). Group prices – when Flight Centre also sends how many people of each unit type are booking, Ventrata prices that exact group. This matters for Booking Size fares and other group pricing. Booking Reservation (`POST /bookings`) and Booking Confirmation (`POST /bookings/{uuid}/confirm`) – the booking comes back with its final retail and net price, so the booking in Ventrata always records the price it was sold at. Typically with Flight Centre: Flight Centre requests `octo/pricing` on all of its availability checks, so it sells at your Ventrata prices. Flight Centre sends the number of people per unit type, so group prices are calculated for the actual booking. ‼️ IMPORTANT – Ask for pricing to be enabled. When you ask Flight Centre to map your products, ask them to enable pricing (`octo/pricing`) as well, or switch it on yourself if you map in Flight Centre's portal. Otherwise it may be off, and Flight Centre won't receive your Ventrata prices. 📗 TIP – If prices on Flight Centre look wrong, check the Flight Centre reseller's pricing in Ventrata first: that's what Flight Centre reads.
Promotions Sync	❌	Your Ventrata promotions don't apply on Flight Centre. Prices on Flight Centre don't include promotions you create in Ventrata. Set up any promotions with Flight Centre directly.
Bookings Sync	✅	Bookings and cancellations made on Flight Centre are created in Ventrata instantly, and customers get Ventrata tickets. This works as follows: Hold: Booking Reservation (`POST /bookings`) – when a customer starts checkout on Flight Centre, Flight Centre sends the product, option, chosen slot (`availabilityId`) and one unit item per person. Ventrata checks capacity again and creates an `ON_HOLD` booking, which holds the places while the customer pays. If there's no longer room, Ventrata rejects the hold. Confirm: Booking Confirmation (`POST /bookings/{uuid}/confirm`) – once payment goes through, Flight Centre confirms the hold, with its own booking reference and the customer's contact details. The booking becomes `CONFIRMED` in Ventrata, and Ventrata sends back your booking reference and the tickets (one per person) or a voucher (one per booking), depending on how your product is set up, each with a QR code and a PDF link. Flight Centre gives these to the customer, who shows them at your entrance like any Ventrata ticket. Expire: if the customer doesn't finish paying, Flight Centre never confirms, and the hold expires on its own and frees the places. Cancel: Booking Cancellation (`POST /bookings/{uuid}/cancel`) – when a customer cancels on Flight Centre, Flight Centre cancels the booking in Ventrata. Ventrata accepts this only if the booking can still be cancelled and the option's cancellation cutoff hasn't passed. Otherwise it rejects the request, and Flight Centre has to contact you. Change: Flight Centre doesn't use Booking Update (`PATCH /bookings/{uuid}`), so a change most likely reaches Ventrata as a cancellation plus a new booking. Typically with Flight Centre: Flight Centre holds places for about 30 minutes while the customer pays (`expirationMinutes`). A typical Flight Centre booking is for about 3 people. It's normal to see more holds than confirmed bookings: holds from customers who don't finish paying simply expire. ‼️ IMPORTANT – Bookings sync one way, from Flight Centre to Ventrata. If you cancel, change or rebook a booking from Flight Centre in Ventrata, for example in the Dashboard, Flight Centre isn't notified. Contact Flight Centre so the booking is cancelled or changed on their side too, or ask the customer to cancel through Flight Centre.
Pickups/Dropoff Sync	✅	Flight Centre sends pickup details with its bookings. This works as follows: `octo/pickups` capability – Flight Centre can see which options offer pickup and their pickup points, and send the customer's pickup point or hotel with the booking. If a hotel doesn't match one of your pickup points, Ventrata saves it with the booking so you can arrange the pickup. Typically with Flight Centre: Flight Centre sends pickup details with its bookings.
Custom Questions Sync	✅ / ❌	Flight Centre sends answers to your booking questions with its bookings. This works as follows: `octo/questions` capability – Flight Centre reads the questions set on your products and sends the customer's answers with the booking, where you see them in Ventrata. Typically with Flight Centre: Flight Centre sends answers to your booking questions.
Extras Sync	❌	Extras and add-ons can't be booked through Flight Centre. Customers can only book your main products and options on Flight Centre. Sell extras separately, for example on arrival.
Redemption Sync	❌	Redemptions aren't reported to Flight Centre. Ventrata doesn't notify Flight Centre when a ticket is scanned or redeemed. Flight Centre only sees a redemption if it reads the booking back from Ventrata.
Pass Walkup Scanning Sync	❌	Flight Centre pass holders can't be scanned at your entrance without a booking. Customers from Flight Centre need a booking made through Flight Centre before they visit.
Gift Card Sync	❌	Ventrata gift cards can't be sold or redeemed through Flight Centre. Gift cards bought in Ventrata can't be used on Flight Centre, and Flight Centre can't sell Ventrata gift cards.

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Flight Centre connection

Delays: availability and prices reach Flight Centre only when it checks, so there's always a short delay after you change something in Ventrata.
Cancellation cutoff: Flight Centre can cancel over the API only before your option's cancellation cutoff. Later cancellations have to be agreed with you.
What Flight Centre can see: only the destinations, products and options allowed on the reseller and the connection, and enabled for sale on the Direct API source. See how to allow or disallow products.
Tickets: Flight Centre issues the Ventrata tickets or voucher it gets on confirmation, so your usual scanning and redemption work as normal.
Test bookings: Flight Centre can send test bookings while it sets up the connection. Test bookings don't use your availability and aren't invoiced.

FAQs

No products are displayed on the connection page.

Verify which destinations, products, and options are allowed on your reseller and connection. Next, confirm that your products and options are enabled for sale on the Direct API source. If the issue persists, contact our Technical Support.

My Ventrata products use Booking Size fares, and pricing isn't working correctly on Flight Centre.

After every fare change, update the product mapping to ensure the partner tier counts are synced with Ventrata. Ensure the fare is enabled for sale over Direct API.

📚 More about Ventrata connections

Partner Information

Flight Centre Travel Group Limited

Southpoint, 275 Grey Street

South Brisbane QLD 4101, Australia

flightcentre.com

Ventrata Partner ID: 45b11cf5-f181-4be1-b90f-763c5ef926bd

Trinity Software Australia Pty. Ltd.

Suite 6, 135 Martyn Street

Parramatta Park QLD 4870, Australia

cobber.one

Ventrata Partner ID: bc427f32-f21f-41be-b900-a07dfc462a58

Flight Centre: Reseller Connection