Planaday builds box office and concierge software for entertainment venues, with a ticketing product that packages several experiences into a single checkout and a concierge tool for guest-facing desks, from offices in Toronto and Las Vegas. Its clients include MGM Resorts, Caesars Entertainment and Ryman Auditorium. For operators, it brings in-destination guests buying at casino resort, hotel and attraction desks during their stay, with concierge staff selling tours and attractions as part of a bundle.

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

To learn more about partnering with Planaday, visit planaday.com.

Primary website	planaday.com
Tags	B2B Marketplace
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Concierge and box office desks at casino resorts and hotels
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Developed by	Planaday (using Ventrata's OCTO API)

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

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

Creating the Planaday Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Planaday connection

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

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

Plan A Day Corp.

planaday.com

Ventrata Partner ID: c1a38d16-cf47-4b47-b592-4552073d5b7f

Planaday: Reseller Connection