Stromma is a European sightseeing operator running canal and harbor boats, hop-on hop-off buses, excursions and dining cruises in 18 cities across Sweden, Norway, Denmark, Finland, the Netherlands and Germany, with its head office in Stockholm. For operators, it brings international leisure visitors to Northern European capitals such as Stockholm, Copenhagen, Oslo, Helsinki and Amsterdam, buying sightseeing and day trips in destination during a sharply seasonal summer peak, with partner attractions and tours sold alongside its own boat and bus departures. Stromma uses Prioticket as their connectivity provider.

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

To learn more about partnering with Stromma, visit stromma.com.

Primary website	stromma.com
Tags	Operator Reselling Others · Sightseeing & Hop-On Hop-Off
Destination markets	🇩🇰 Denmark · 🇫🇮 Finland · 🇩🇪 Germany · 🇳🇱 Netherlands · 🇳🇴 Norway · 🇸🇪 Sweden
Source markets	🌎 Global
Specialties	Boat, bus and dining cruise sightseeing in Nordic capitals
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Developed by	Prioticket (using Ventrata's OCTO API)

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

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

Creating the Stromma Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

This section is for anyone who wants to know exactly how the Stromma connection works: which Ventrata OCTO API calls Stromma 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: Stromma 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 Stromma, so anything you change in Ventrata reaches Stromma the next time it checks.

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Stromma connection

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

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

Stromma Turism & Sjofart AB

Svensksundsvagen 19, SE-111 49 Stockholm

Sweden

stromma.com

Ventrata Partner ID: 24a1726d-1f20-4f70-9db6-873144b09351

Prioticket B.V.

Prins Hendrikkade 21, 1012 TL Amsterdam

Netherlands

prioticket.com

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

Stromma: Reseller Connection