Kliktix is a curated New York City ticketing and distribution platform, selling observatories, harbor cruises, bus tours, museums, walking tours and city passes through a Times Square ticket center, hotel and concierge desks and its mobile-ticket website. For operators, it brings walk-up and same-day visitors who decide once they are in Manhattan, a last-minute buying moment served in person at Times Square and through concierge recommendations. Kliktix uses Prioticket as their connectivity provider.

Connecting Kliktix to Ventrata syncs your availability and prices and delivers bookings, changes and cancellations with tickets issued automatically. Kliktix runs on Prioticket, and receives your products through its certified integration with Ventrata's OCTO API.

To learn more about partnering with Kliktix, visit kliktix.com.

Primary website	kliktix.com
Tags	Offline & Retail Channel
Destination markets	🇺🇸 US
Source markets	🌎 Global
Specialties	Walk-up and same-day New York City sightseeing sales
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$10k+
Developed by	Prioticket (using Ventrata's OCTO API)

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

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

Creating the Kliktix Connection

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

Before you begin:

You must have a commercial agreement with Kliktix for them to sell your products. To inquire about partnering with them, contact them via kliktix.com. To start one, submit the form at kliktix.com/suppliers or contact your KLIKTIX contact.
You must have Kliktix 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 Kliktix (powered by Prioticket) from the list of partners.
Select Kliktix 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 Kliktix 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 Kliktix

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

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

📗 TIP

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

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

Connection Features Detailed

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

In short: Kliktix pulls everything it needs from Ventrata. It reads your products, checks your availability (and your prices, when it asks for them), and sends bookings and cancellations. Ventrata doesn't push changes to Kliktix, so anything you change in Ventrata reaches Kliktix the next time it checks.

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Kliktix connection

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

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

KLIKTIX LLC

111-14 76th Ave, #315, Forest Hills, NY 11375

United States

kliktix.com

Ventrata Partner ID: a470727f-56e1-4ac2-8fa2-ffd6c6b6a0df

Prioticket B.V.

Prins Hendrikkade 21, 1012 TL Amsterdam

Netherlands

prioticket.com

Ventrata Partner ID: 8347e498-1afe-48e1-9d99-8b2d1e0069fb

Kliktix: Reseller Connection