WeShare is a Paris-based travel platform packaging accommodation, activities, airport transfers, Swiss rail passes and Disneyland Paris products across European cities, with coverage extending into Japan, Thailand, Singapore, Indonesia and Australia. For operators, it brings trade demand first, groups, fixed departures, trade fairs, MICE and FIT booked by agents through its agent portal, alongside direct consumer sales.

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

To learn more about partnering with WeShare, visit weshare.pro.

Primary website	weshare.pro
Tags	B2B Marketplace
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Agent-booked groups, fixed departures and MICE
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Developed by	WeShare (using Ventrata's OCTO API)

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

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

Creating the WeShare Connection

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

Before you begin:

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

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

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

📗 TIP

WeShare 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 WeShare Connection

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the WeShare connection

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

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

WeShare

weshare.pro

Ventrata Partner ID: 3664f124-a58f-430a-bbad-dd5848dff65f

WeShare: Reseller Connection