Ninkio is a Paris-based affiliate platform pairing tour and activity suppliers with travel creators: Instagram, TikTok and YouTube accounts, bloggers and travel media sites that sell experiences to their own audiences through a storefront or embedded widget. For operators, it brings creator-driven demand worldwide, followers who book an experience they have just seen in content, with Ninkio handling partner matching, bookings and monthly creator payouts.

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

To learn more about partnering with Ninkio, visit ninkio.co.

Primary website	ninkio.co
Tags	Discovery & Affiliates
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Creator and influencer-driven sales
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Developed by	Ninkio (using Ventrata's OCTO API)

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

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

Creating the Ninkio Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Ninkio connection

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

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

Ninkio SAS

47 rue Vivienne, 75002 Paris

France

ninkio.co

Ventrata Partner ID: e5b01691-3b64-45c4-b09e-c81890debad0

Ninkio: Reseller Connection