Day Experience is a French online booking platform for tourist activities, listing over 20,000 activities in more than 500 destinations including Paris, Rome, New York, Dubai and Tokyo, from guided tours and skip-the-line museum tickets to city passes. Alongside direct consumer sales with francophone support, it recruits travel agencies and tour operators through a reseller program. For operators, it brings French-speaking leisure travelers booking ahead of city trips in Europe and beyond, together with the trade buyers it supplies, so demand arrives both direct and through agencies.

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

To learn more about partnering with Day Experience, visit day-experience.com.

Primary website	day-experience.com
Tags	B2B Marketplace
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	French-speaking travelers, booking direct and through agencies
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$10k+
Ventrata Booked Suppliers (last 12 months)	5+
Developed by	Day Experience (using Ventrata's OCTO API)

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

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

Creating the Day Experience Connection

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

Before you begin:

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

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

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

📗 TIP

Day Experience 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 Day Experience Connection

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Day Experience connection

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

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

Day Experience SAS

52 rue de Malte, 75011 Paris

France

day-experience.com

Ventrata Partner ID: 744c1be8-afd9-431b-9950-94316c598b27

Day Experience: Reseller Connection