Skip to main content

VELTRA: Reseller Connection

Connect VELTRA to Ventrata to sync availability and prices and receive bookings instantly. Japanese outbound travelers who book early.

VELTRA logo powered by Globick icon Globick

 

VELTRA is a Tokyo-based online travel agency (OTA) for tours and activities, carrying more than 20,000 experiences across 150 countries. For operators, it brings Japanese outbound travelers, close to 90% of its demand, a source market that books early, buys in Japanese and rarely appears in volume on Western platforms. VELTRA uses Globick as their connectivity provider.

 

Connecting VELTRA to Ventrata will sync your availability and prices and deliver bookings, changes and cancellations with tickets issued automatically. VELTRA runs on Globick, and receives your products through its certified integration with Ventrata's OCTO API.

 

To learn more about partnering with VELTRA, visit veltra.com.

 

📒 NOTE

VELTRA connects to Ventrata through Globick, a channel manager that runs the integration on its behalf. As it isn't a direct connection, some functionality or content may be limited for reasons outside Ventrata's control.

 

Primary website

veltra.com

Tags

OTA · Tours & Activities OTA

Destination markets

🌎 Global

Source markets

🇯🇵 Japan

Specialties

Japanese outbound travelers who book early

Connection features

Availability Sync · Pricing Sync · Bookings Sync

Developed by

Globick (using Ventrata's OCTO API)

 

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

  • Availability Sync – VELTRA checks your live availability in Ventrata.

  • Pricing Sync – VELTRA gets your prices from your reseller pricing in Ventrata.

  • Bookings Sync – bookings, updates and cancellations from VELTRA are created in Ventrata instantly, and customers get Ventrata tickets.

 

Creating the VELTRA Connection

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

Before you begin:

  • You must have a commercial agreement with VELTRA for them to sell your products. To inquire about partnering with them, contact them via veltra.com.

  • You must have VELTRA 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.

 

  1. In Ventrata Dashboard, go to Connections → Connections, click + New Connection, and select VELTRA (powered by Globick) from the list of partners.

  2. Select VELTRA 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.

  3. (Optional) You can also set the connection Name of your choosing, which may be helpful if you plan to have multiple VELTRA connections and would like to differentiate between them more easily in the future.

  4. 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 VELTRA

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

 

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

 

📗 TIP

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

  • Allow or disallow products: limit which destinations, products and options VELTRA can access. See how to allow or disallow products.

  • Rename the connection to tell several VELTRA connections apart.

 

Connection Features Detailed

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

 

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

 

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

 

Product Mapping

❌

You can't map products from Ventrata. VELTRA maps them on its side, through your account manager or VELTRA's portal.

This works as follows:

  • Get Products (GET /products) – when VELTRA 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}) – VELTRA re-reads a single product to pick up changes to its options, units, booking cutoffs and settings.

  • Mapping on VELTRA's side – VELTRA links each Ventrata option and unit to its own listing and ticket types. Your VELTRA account manager does this for you, or you do it in VELTRA's own portal if VELTRA offers one. You only share the connection's API key.

 

Typically with VELTRA:

  • VELTRA reads your full product list about once a day.

  • It re-reads each product about every 2 hours.

 

What this means for you: VELTRA can only sell what it has mapped. When you add a product, option or unit in Ventrata, VELTRA may see it on its next refresh, but it won't sell it until it's mapped. So tell your VELTRA account manager whenever you add one.

Content Sync

✅ / ❌

VELTRA can read your product content, such as descriptions and images, from Ventrata.

This works as follows:

  • octo/content capability – when VELTRA 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 VELTRA on its next product refresh.

 

Typically with VELTRA:

  • VELTRA requests octo/content.

Availability Sync

✅

VELTRA checks your live availability in Ventrata. Ventrata doesn't push availability changes to VELTRA.

This works as follows:

  • Availability Check (POST /availability) – VELTRA 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 VELTRA 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 VELTRA can't overbook a slot that has just sold out, even if its stored availability is slightly out of date.

 

Typically with VELTRA:

  • Availability Check: VELTRA checks your products throughout the day, usually starting 33 days ahead and covering 4 days per request, looks up to about 5 months ahead and re-checks the same product and dates about every 18 hours.

  • Availability Calendar: VELTRA checks your products throughout the day, usually starting 8 days ahead and covering 8 days per request, looks up to about 6 months ahead and re-checks the same product and dates about every 14 hours.

  • Checks are busiest between 10:00 and 16:00 UTC, which suggests most checks are live, as customers browse VELTRA.

 

What this means for you: when you close a date, change capacity or sell out in Ventrata, VELTRA shows it after its next check. For dates it checks regularly, that's within about 14 hours. Dates further ahead are usually checked less often.

Pricing Sync

✅

Your prices come back with every availability check, once VELTRA asks for them with the octo/pricing capability.

This works as follows:

  • octo/pricing capability – VELTRA 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 VELTRA, both from the reseller's pricing in Ventrata (retail and wholesale/commission).

  • Group prices – when VELTRA 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 VELTRA:

  • VELTRA requests octo/pricing on all of its availability checks, so it sells at your Ventrata prices.

  • VELTRA 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 VELTRA to map your products, ask them to enable pricing (octo/pricing) as well, or switch it on yourself if you map in VELTRA's portal. Otherwise it may be off, and VELTRA won't receive your Ventrata prices.

📗 TIP – If prices on VELTRA look wrong, check the VELTRA reseller's pricing in Ventrata first: that's what VELTRA reads.

Promotions Sync

❌

Your Ventrata promotions don't apply on VELTRA.

Prices on VELTRA don't include promotions you create in Ventrata. Set up any promotions with VELTRA directly.

Bookings Sync

✅

Bookings and cancellations made on VELTRA are created in Ventrata instantly, and customers get Ventrata tickets.

This works as follows:

  1. Hold: Booking Reservation (POST /bookings) – when a customer starts checkout on VELTRA, VELTRA 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.

  2. Confirm: Booking Confirmation (POST /bookings/{uuid}/confirm) – once payment goes through, VELTRA 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. VELTRA gives these to the customer, who shows them at your entrance like any Ventrata ticket.

  3. Expire: if the customer doesn't finish paying, VELTRA never confirms, and the hold expires on its own and frees the places.

  4. Cancel: Booking Cancellation (POST /bookings/{uuid}/cancel) – when a customer cancels on VELTRA, VELTRA 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 VELTRA has to contact you.

  5. Change: VELTRA doesn't use Booking Update (PATCH /bookings/{uuid}), so a change most likely reaches Ventrata as a cancellation plus a new booking.

 

Typically with VELTRA:

  • VELTRA doesn't set a hold time, so the default hold time applies.

  • A typical VELTRA booking is for about 1 person.

  • It's normal to see more holds than confirmed bookings: holds from customers who don't finish paying simply expire.

  • VELTRA also checks the bookings it has made, with Get Booking (GET /bookings/{uuid}) about every 14 hours, for example to reconcile its records.

 

‼️ IMPORTANT – Bookings sync one way, from VELTRA to Ventrata. If you cancel, change or rebook a booking from VELTRA in Ventrata, for example in the Dashboard, VELTRA isn't notified. Contact VELTRA so the booking is cancelled or changed on their side too, or ask the customer to cancel through VELTRA.

Pickups/Dropoff Sync

✅ / ❌

VELTRA sends pickup details with its bookings.

This works as follows:

  • octo/pickups capability – VELTRA can see which options offer pickup and their pickup points, and send the customer's pickup point or hotel with the booking.

  • If a hotel doesn't match one of your pickup points, Ventrata saves it with the booking so you can arrange the pickup.

 

Typically with VELTRA:

  • VELTRA sends pickup details with its bookings.

Custom Questions Sync

❌

VELTRA doesn't send answers to your booking questions.

If you rely on booking questions, for example names or dietary needs, check with VELTRA how it collects that information.

Extras Sync

❌

Extras and add-ons can't be booked through VELTRA.

Customers can only book your main products and options on VELTRA. Sell extras separately, for example on arrival.

Redemption Sync

❌

Redemptions aren't reported to VELTRA.

Ventrata doesn't notify VELTRA when a ticket is scanned or redeemed. VELTRA only sees a redemption if it reads the booking back from Ventrata.

Pass Walkup Scanning Sync

❌

VELTRA pass holders can't be scanned at your entrance without a booking.

Customers from VELTRA need a booking made through VELTRA before they visit.

Gift Card Sync

❌

Ventrata gift cards can't be sold or redeemed through VELTRA.

Gift cards bought in Ventrata can't be used on VELTRA, and VELTRA can't sell Ventrata gift cards.

✅ supported · ✅ / ❌ limited · ❌ not supported

 

Good to know: limits and details of the VELTRA connection

  • Delays: availability and prices reach VELTRA only when it checks, so there's always a short delay after you change something in Ventrata.

  • Cancellation cutoff: VELTRA can cancel over the API only before your option's cancellation cutoff. Later cancellations have to be agreed with you.

  • What VELTRA 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: VELTRA issues the Ventrata tickets or voucher it gets on confirmation, so your usual scanning and redemption work as normal.

  • Test bookings: VELTRA 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 VELTRA.

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

VELTRA Corporation (ベルトラ株式会社)

5F Nippon Life Nihonbashi Building, 2-13-12 Nihonbashi, Chuo-ku, Tokyo 103-0027

Japan

veltra.com

 

Ventrata Partner ID: d35fa5f4-49e9-4564-bca3-bc5cf03419d8

 

Globick

Calle Numancia, 73, 5C, 08029 Barcelona

Spain

globick.com

 

Ventrata Partner ID: 0ed2e173-4b56-4ab7-9050-2b8cbe55cab9

Related Articles
Did this answer your question?