Tamice is a Korean-language online travel agency (OTA) for travelers heading to the United States, centered on New York and built around its Big Apple Pass multi-attraction pass, alongside Broadway tickets, helicopter tours, US SIM cards and Woodbury outlet shopping trips. For operators, it brings Korean outbound leisure travelers who buy passes and admissions before departure, planning the trip in Korean weeks ahead of arrival.

Connecting Tamice to Ventrata will sync your availability and prices and deliver bookings, changes and cancellations with tickets issued automatically.

To learn more about partnering with Tamice, visit tamice.com.

Primary website	tamice.com
Tags	Multi-Attraction Pass
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Korean travelers to New York buying passes before departure
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$100k+
Ventrata Booked Suppliers (last 12 months)	10+
Developed by	Tamice (using Ventrata's OCTO API)

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

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

Creating the Tamice Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ❌ not supported

Good to know: limits and details of the Tamice connection

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

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

Tamice

151 W 46th St, Suite 1002

New York, 10036, United States

tamice.com

Ventrata Partner ID: 7496af02-5044-4497-9b08-e994ed425dd6

Tamice: Reseller Connection