Bilet.com is a Turkish online travel agency (OTA) selling bus, ferry and flight tickets alongside event and attraction tickets, from concerts and theater to aquariums, theme parks, museums and cable cars, priced in Turkish lira and TURSAB-accredited. For operators, it brings domestic Turkish travelers booking tickets with their transport, including students and bank-card campaign members, plus outbound travelers planning Greek island trips from Turkey.

Connecting Bilet.com to Ventrata syncs your availability and prices and delivers bookings, changes and cancellations with tickets issued automatically.

To learn more about partnering with Bilet.com, visit bilet.com.

Primary website	bilet.com
Tags	Travel Agent · Event & Festival Ticketing
Destination markets	🇹🇷 Türkiye
Source markets	🇹🇷 Türkiye
Specialties	Domestic Turkish travelers booking with their transport
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$10k+
Developed by	Bilet.com (using Ventrata's OCTO API)

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

Availability Sync – Bilet.com checks your live availability in Ventrata.
Pricing Sync – Bilet.com gets your prices from your reseller pricing in Ventrata.
Bookings Sync – bookings, updates and cancellations from Bilet.com are created in Ventrata instantly, and customers get Ventrata tickets.

Creating the Bilet.com Connection

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

Before you begin:

You must have a commercial agreement with Bilet.com for them to sell your products. To inquire about partnering with them, contact them via bilet.com.
You must have Bilet.com 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 Bilet.com from the list of partners.
Select Bilet.com 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 Bilet.com 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 Bilet.com

Securely share the OCTO API key shown on the connection you've created to your Bilet.com 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 Bilet.com team to complete this.

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

📗 TIP

Bilet.com 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 Bilet.com Connection

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

Connection Features Detailed

This section is for anyone who wants to know exactly how the Bilet.com connection works: which Ventrata OCTO API calls Bilet.com makes, when it makes them, and what that means for you. Each call links to Ventrata's API documentation.

In short: Bilet.com 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 Bilet.com, so anything you change in Ventrata reaches Bilet.com the next time it checks.

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

Product Mapping	❌	You can't map products from Ventrata. Bilet.com maps them on its side, through your account manager or Bilet.com's portal. This works as follows: Get Products (`GET /products`) – when Bilet.com 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}`) – Bilet.com re-reads a single product to pick up changes to its options, units, booking cutoffs and settings. Mapping on Bilet.com's side – Bilet.com links each Ventrata option and unit to its own listing and ticket types. Your Bilet.com account manager does this for you, or you do it in Bilet.com's own portal if Bilet.com offers one. You only share the connection's API key. Typically with Bilet.com: It re-reads each product about every 10 minutes. What this means for you: Bilet.com can only sell what it has mapped. When you add a product, option or unit in Ventrata, Bilet.com may see it on its next refresh, but it won't sell it until it's mapped. So tell your Bilet.com account manager whenever you add one.
Content Sync	✅ / ❌	Bilet.com can read your product content, such as descriptions and images, from Ventrata. This works as follows: `octo/content` capability – when Bilet.com 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 Bilet.com on its next product refresh. Typically with Bilet.com: Bilet.com requests `octo/content`.
Availability Sync	✅	Bilet.com checks your live availability in Ventrata. Ventrata doesn't push availability changes to Bilet.com. This works as follows: Availability Check (`POST /availability`) – Bilet.com 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 Bilet.com needs to book that slot. Check at booking – when a customer books, Ventrata checks capacity again before it creates the booking, so Bilet.com can't overbook a slot that has just sold out, even if its stored availability is slightly out of date. Typically with Bilet.com: Availability Check: Bilet.com checks your products throughout the day, usually starting tomorrow and covering a single day per request, looks up to 44 days ahead and re-checks the same product and dates about every 2 hours. Checks are busiest between 08:00 and 14:00 UTC, which suggests most checks are live, as customers browse Bilet.com. What this means for you: when you close a date, change capacity or sell out in Ventrata, Bilet.com shows it after its next check. For dates it checks regularly, that's within about 2 hours. Dates further ahead are usually checked less often.
Pricing Sync	✅	Your prices come back with every availability check, once Bilet.com asks for them with the octo/pricing capability. This works as follows: `octo/pricing` capability – Bilet.com 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 Bilet.com, both from the reseller's pricing in Ventrata (retail and wholesale/commission). Group prices – when Bilet.com 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 Bilet.com: Bilet.com requests `octo/pricing` on all of its availability checks, so it sells at your Ventrata prices. Bilet.com 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 Bilet.com to map your products, ask them to enable pricing (`octo/pricing`) as well, or switch it on yourself if you map in Bilet.com's portal. Otherwise it may be off, and Bilet.com won't receive your Ventrata prices. 📗 TIP – If prices on Bilet.com look wrong, check the Bilet.com reseller's pricing in Ventrata first: that's what Bilet.com reads.
Promotions Sync	✅ / ❌	Your Ventrata promotions can apply to Bilet.com prices and bookings. This works as follows: `octo/offers` capability – with it, Ventrata applies your eligible promotions to availability prices and to bookings, and Bilet.com can also send a promo code (`offerCode`). Promotions work together with pricing, so they need `octo/pricing` as well. This covers promotions you create in Ventrata (supplier-initiated promotions). Typically with Bilet.com: Bilet.com requests `octo/offers`.
Bookings Sync	✅	Bookings and cancellations made on Bilet.com 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 Bilet.com, Bilet.com 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, Bilet.com 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. Bilet.com gives these to the customer, who shows them at your entrance like any Ventrata ticket. Expire: if the customer doesn't finish paying, Bilet.com 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 Bilet.com, Bilet.com 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 Bilet.com has to contact you. Change: Bilet.com doesn't use Booking Update (`PATCH /bookings/{uuid}`), so a change most likely reaches Ventrata as a cancellation plus a new booking. Typically with Bilet.com: Bilet.com holds places for about 30 minutes while the customer pays (`expirationMinutes`). A typical Bilet.com booking is for about 2 people. It's normal to see more holds than confirmed bookings: holds from customers who don't finish paying simply expire. Bilet.com also checks the bookings it has made, with Get Booking (`GET /bookings/{uuid}`) about every 10 hours, for example to reconcile its records. ‼️ IMPORTANT – Bookings sync one way, from Bilet.com to Ventrata. If you cancel, change or rebook a booking from Bilet.com in Ventrata, for example in the Dashboard, Bilet.com isn't notified. Contact Bilet.com so the booking is cancelled or changed on their side too, or ask the customer to cancel through Bilet.com.
Pickups/Dropoff Sync	❌	Bilet.com doesn't send pickup or drop-off details with its bookings. If your products include pickups, check with Bilet.com how it collects pickup details, or arrange them with the customer.
Custom Questions Sync	❌	Bilet.com doesn't send answers to your booking questions. If you rely on booking questions, for example names or dietary needs, check with Bilet.com how it collects that information.
Extras Sync	❌	Extras and add-ons can't be booked through Bilet.com. Customers can only book your main products and options on Bilet.com. Sell extras separately, for example on arrival.
Redemption Sync	❌	Redemptions aren't reported to Bilet.com. Ventrata doesn't notify Bilet.com when a ticket is scanned or redeemed. Bilet.com only sees a redemption if it reads the booking back from Ventrata.
Pass Walkup Scanning Sync	❌	Bilet.com pass holders can't be scanned at your entrance without a booking. Customers from Bilet.com need a booking made through Bilet.com before they visit.
Gift Card Sync	❌	Ventrata gift cards can't be sold or redeemed through Bilet.com. Gift cards bought in Ventrata can't be used on Bilet.com, and Bilet.com can't sell Ventrata gift cards.

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Bilet.com connection

Delays: availability and prices reach Bilet.com only when it checks, so there's always a short delay after you change something in Ventrata.
Cancellation cutoff: Bilet.com can cancel over the API only before your option's cancellation cutoff. Later cancellations have to be agreed with you.
What Bilet.com 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: Bilet.com issues the Ventrata tickets or voucher it gets on confirmation, so your usual scanning and redemption work as normal.
Test bookings: Bilet.com 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 Bilet.com.

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

Bilet.com

bilet.com

Ventrata Partner ID: 6f47c5e2-5203-44c9-901c-cc68fc856d55

Bilet.com: Reseller Connection