Baja Bikes is a Dutch bike tour specialist offering guided city rides with Dutch-speaking guides, plus self-guided tours and rentals, in around 300 destinations worldwide. For operators, it brings Dutch-language source-market demand for active city sightseeing, more than a million customers served since 2005, booking guided rides and bike rentals for city breaks across Europe and beyond.

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

To learn more about partnering with Baja Bikes, visit bajabikes.eu.

Primary website	bajabikes.eu
Tags	OTA · Tours & Activities OTA · Adventure & Outdoor · Audio Guides & Self-Guided
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Dutch-speaking source market for bike tours
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$100k+
Developed by	Baja Bikes (using Ventrata's OCTO API)

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

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

Creating the Baja Bikes Connection

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

Before you begin:

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

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

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

📗 TIP

Baja Bikes 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 Baja Bikes Connection

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

Connection Features Detailed

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

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

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

Product Mapping	❌	You can't map products from Ventrata. Baja Bikes maps them on its side, through your account manager or Baja Bikes's portal. This works as follows: Get Products (`GET /products`) – when Baja Bikes 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}`) – Baja Bikes re-reads a single product to pick up changes to its options, units, booking cutoffs and settings. Mapping on Baja Bikes's side – Baja Bikes links each Ventrata option and unit to its own listing and ticket types. Your Baja Bikes account manager does this for you, or you do it in Baja Bikes's own portal if Baja Bikes offers one. You only share the connection's API key. Typically with Baja Bikes: Baja Bikes reads your full product list about every 2 hours. It re-reads each product every few minutes. What this means for you: Baja Bikes can only sell what it has mapped. When you add a product, option or unit in Ventrata, Baja Bikes may see it on its next refresh, but it won't sell it until it's mapped. So tell your Baja Bikes account manager whenever you add one.
Content Sync	✅ / ❌	Baja Bikes can read your product content, such as descriptions and images, from Ventrata. This works as follows: `octo/content` capability – when Baja Bikes 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 Baja Bikes on its next product refresh. Typically with Baja Bikes: Baja Bikes requests `octo/content`.
Availability Sync	✅	Baja Bikes checks your live availability in Ventrata. Ventrata doesn't push availability changes to Baja Bikes. This works as follows: Availability Check (`POST /availability`) – Baja Bikes 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 Baja Bikes needs to book that slot. Check at booking – when a customer books, Ventrata checks capacity again before it creates the booking, so Baja Bikes can't overbook a slot that has just sold out, even if its stored availability is slightly out of date. Typically with Baja Bikes: Availability Check: Baja Bikes checks your products throughout the day, usually starting 48 days ahead and covering 17 days per request, looks up to about 10 months ahead and re-checks the same product and dates about every 2 hours. Checks are spread through the day with no strong peak, which suggests a mix of scheduled syncs and live customer searches. What this means for you: when you close a date, change capacity or sell out in Ventrata, Baja Bikes 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 Baja Bikes asks for them with the octo/pricing capability. This works as follows: `octo/pricing` capability – Baja Bikes 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 Baja Bikes, both from the reseller's pricing in Ventrata (retail and wholesale/commission). Group prices – when Baja Bikes 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 Baja Bikes: Baja Bikes requests `octo/pricing` on all of its availability checks, so it sells at your Ventrata prices. Baja Bikes doesn't send the number of people per unit type, so prices come back per person, and group pricing such as Booking Size fares may not show correctly on Baja Bikes. ‼️ IMPORTANT – Ask for pricing to be enabled. When you ask Baja Bikes to map your products, ask them to enable pricing (`octo/pricing`) as well, or switch it on yourself if you map in Baja Bikes's portal. Otherwise it may be off, and Baja Bikes won't receive your Ventrata prices. 📗 TIP – If prices on Baja Bikes look wrong, check the Baja Bikes reseller's pricing in Ventrata first: that's what Baja Bikes reads.
Promotions Sync	❌	Your Ventrata promotions don't apply on Baja Bikes. Prices on Baja Bikes don't include promotions you create in Ventrata. Set up any promotions with Baja Bikes directly.
Bookings Sync	✅	Bookings and cancellations made on Baja Bikes 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 Baja Bikes, Baja Bikes 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, Baja Bikes 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. Baja Bikes gives these to the customer, who shows them at your entrance like any Ventrata ticket. Expire: if the customer doesn't finish paying, Baja Bikes 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 Baja Bikes, Baja Bikes 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 Baja Bikes has to contact you. Change: Baja Bikes doesn't use Booking Update (`PATCH /bookings/{uuid}`), so a change most likely reaches Ventrata as a cancellation plus a new booking. Typically with Baja Bikes: Baja Bikes doesn't set a hold time, so the default hold time applies. A typical Baja Bikes booking is for about 3 people. ‼️ IMPORTANT – Bookings sync one way, from Baja Bikes to Ventrata. If you cancel, change or rebook a booking from Baja Bikes in Ventrata, for example in the Dashboard, Baja Bikes isn't notified. Contact Baja Bikes so the booking is cancelled or changed on their side too, or ask the customer to cancel through Baja Bikes.
Pickups/Dropoff Sync	❌	Baja Bikes doesn't send pickup or drop-off details with its bookings. If your products include pickups, check with Baja Bikes how it collects pickup details, or arrange them with the customer.
Custom Questions Sync	❌	Baja Bikes doesn't send answers to your booking questions. If you rely on booking questions, for example names or dietary needs, check with Baja Bikes how it collects that information.
Extras Sync	❌	Extras and add-ons can't be booked through Baja Bikes. Customers can only book your main products and options on Baja Bikes. Sell extras separately, for example on arrival.
Redemption Sync	❌	Redemptions aren't reported to Baja Bikes. Ventrata doesn't notify Baja Bikes when a ticket is scanned or redeemed. Baja Bikes only sees a redemption if it reads the booking back from Ventrata.
Pass Walkup Scanning Sync	❌	Baja Bikes pass holders can't be scanned at your entrance without a booking. Customers from Baja Bikes need a booking made through Baja Bikes before they visit.
Gift Card Sync	❌	Ventrata gift cards can't be sold or redeemed through Baja Bikes. Gift cards bought in Ventrata can't be used on Baja Bikes, and Baja Bikes can't sell Ventrata gift cards.

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Baja Bikes connection

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

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

Baja Bikes Holding B.V.

Bahialaan

Rotterdam, Netherlands

bajabikes.eu

Ventrata Partner ID: a25efe23-5971-4da2-b32f-273e8e8bb2af

Baja Bikes: Reseller Connection