Picniq is a UK online travel agency (OTA) for family days out, selling discounted admission to theme parks, zoos, museums and entertainment venues plus Disneyland Paris packages, ABTA-protected and with a loyalty scheme alongside deals content and email. For operators, it brings UK domestic, price-sensitive parents booking for school holidays and weekends, reached through its deals newsletters and loyalty members, with theme park and attraction admission the main purchases.

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

To learn more about partnering with Picniq, visit tickets.picniq.co.uk.

Primary website	tickets.picniq.co.uk
Tags	Family Experiences · Theme Park Tickets
Destination markets	🇬🇧 UK
Source markets	🇬🇧 UK
Specialties	Discounted family days out and theme park tickets
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$10k+
Ventrata Booked Suppliers (last 12 months)	5+
Developed by	Picniq (using Ventrata's OCTO API)

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

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

Creating the Picniq Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Picniq connection

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

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

PICNIQ LIMITED

Space House, 22-24 Oxford Road, Bournemouth, Dorset, England, BH8 8EZ

United Kingdom

tickets.picniq.co.uk

Ventrata Partner ID: fbb16b87-570d-4345-b17a-1a0bb12147a7

Picniq: Reseller Connection