BeMyGuest is a Singapore-based technology and distribution company for tours, activities and attractions, running a distribution network, a booking system and the myVisitPass multi-attraction pass product. For operators, it brings Asian and global reseller demand: online and offline travel agents, groups and corporate buyers through its agents marketplace and booking API, plus B2C, walk-in and corporate group sales through the e-commerce and point-of-sale modules its operator clients run.

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

To learn more about partnering with BeMyGuest, visit bemyguest.com.sg.

Primary website	bemyguest.com.sg
Tags	B2B Marketplace
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Asian travel agents, groups and corporate buyers
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$1M+
Ventrata Booked Suppliers (last 12 months)	10+
Developed by	BeMyGuest (using Ventrata's OCTO API)

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

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

Creating the BeMyGuest Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the BeMyGuest connection

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

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

BeMyGuest Pte. Ltd.

36 Robinson Road, #04-108, City House

Singapore 068877

bemyguest.com.sg

Ventrata Partner ID: 552394dc-a174-4b4f-8f73-938cec82c6cc

BeMyGuest: Reseller Connection