Skip to main content

Distribusion Connector

Written by Product Management

Overview

This article describes the use cases and key characteristics of Nezasa's Distribusion Connector.

Distribusion is a Berlin-based ground transport aggregation platform, connecting to roughly 3,000 rail, bus, and ferry carriers worldwide — including Deutsche Bahn, SNCF, Trenitalia, Amtrak, Eurostar, Flixtrain, and WestBahn. The connector gives TripBuilder real-time search, pricing, and booking for one-way ground transport journeys. Return (round-trip) journeys are not yet supported.

⚠️ Requirement: The Distribusion connector requires the new Ground Transport UX in TripBuilder. Please ensure this is enabled for your account before configuring the integration. Contact Nezasa if you are unsure.

Supported Use Cases

Use Case

Support

Search Offers

✅ Supported

Get Offer Details

✅ Supported

Availability Check

✅ Supported

Book

✅ Supported

Cancel

✅ Supported

Booking Change

⚠️ Supported via Cockpit booking change where a cancellation and re-booking is required.

Name Change

⚠️ Supported via Cockpit booking change where a cancellation and re-booking is required.

Reconciliation / Webhooks

✅ Supported

Cancellation Policies via API

✅ Supported as part of the description of each offer

Offer Terms & Conditions via API

✅ Supported as part of the description of each offer

Prerequisites

Before you can activate the Distribusion connector, you need:

  1. A commercial agreement with Distribusion: commercial terms (commission, billing) are agreed directly between you and Distribusion. If you don't have an agreement yet, reach out to your Distribusion representative to get set up.

  2. A Nezasa subscription: The connector is available on eligible Nezasa plans. Contact your Nezasa account manager if you're unsure.

Setting Up New Credentials

Distribusion issues credentials on a per-client basis: an API key and a Retailer Partner Number (RPN) and webhook secret — potentially multiple sets if you operate across several markets or distribution channels. Distribusion's technical team transfers your production API key, RPN, and webhook secret directly to you via a secure, encrypted handover, with the Nezasa Operations Team kept in copy — so no extra step is needed on your side to share these with Nezasa.

If you operate a main-agent / sub-agent structure (e.g. a head office with individual branch agencies), this setup is supported by Distribusion

💡 If your commercial setup with Distribusion is not yet in place, reach out to your Distribusion account representative to get started.

Testing

To test the Distribusion connector in a staging environment, Nezasa will configure your credentials against Distribusion's staging endpoint.

When using the testing environment, keep the following in mind:

  • Ensure that test bookings are cancelled after testing, including in the staging environment.

  • Check with your Distribusion contact if additional testing requirements or procedures apply on their side.

Distribusion Specifics

Transport Types

Distribusion covers rail, bus, and ferry — connecting to roughly 3,000 carriers worldwide, including Deutsche Bahn, SNCF, Trenitalia, Amtrak, Eurostar, Flixtrain, and WestBahn. Ferry content currently focuses on Asia (Philippines, Vietnam); major European ferry operators are expected to be added in the coming months.

Carriers are enable through the contract signing with Distribusion

Pickup & Drop-Off Locations

Distribusion supports the following transfer scenarios:

  • Airport → Point (e.g., flight arrival to city)

  • Point → Airport (e.g., city to flight departure)

  • Point → Point (e.g., city-to-city)

Searches are location-to-location rather than station-to-station — results include all matching offers across every station within the selected locations, not just a single named station.

💡 Tip — Airport transfers: For connections to or from an airport, if no flight is selected, the system defaults to a departure time of 9:00 AM. We recommend selecting the flight first so that TripBuilder can automatically determine the correct transfer time based on the actual arrival or departure time at the airport.

For airport transfers with a linked flight, TripBuilder sends the flight number and airport IATA code in the ground transport booking request so Distribusion can identify the relevant flight context for pickup coordination.

Cancellation Policy

Cancellation terms are carrier-specific — there is no single platform-wide cancellation policy. Terms are displayed on the UI in the offer details section.

Vouchers & Booking Confirmation

Once a booking is confirmed, a PDF voucher is generated for the traveller. Seats are not selectable during booking — they are assigned at random by the carrier, and the assigned seat is included on the voucher.

FAQ

Q: Does the connector support return (round-trip) journeys?
A: Not currently. Only one-way ground transport journeys are supported.

Q: Can my customer choose a specific seat?
A: No. Seats are assigned at random by the carrier and shown on the traveller's voucher.

Q: Are ferries supported?
A: Yes, but coverage currently focuses on Asia (Philippines, Vietnam). Major European ferry operators are expected to be added in the coming months.

Q: Can each of my distribution channels or markets have separate Distribusion credentials?
A: Yes. TripBuilder supports multiple Contract IDs, allowing each market or distribution channel to be configured with its own credentials independently. Contact Nezasa to set this up.

Did this answer your question?