Negotiated & Corporate Fares

Distribusion ensures fare parity across all ground transportation carriers, meaning that the fares offered through our platform match those available directly from the carriers. This allows users to access standardized pricing without discrepancies.

Additionally, Distribusion supports the retrieval of negotiated fares, enabling companies to offer custom pricing agreements they’ve established with carriers. This feature is particularly valuable for businesses with high-volume travel needs or partnerships, as it streamlines the booking process and ensures their negotiated rates are seamlessly integrated.

Where corporate codes come from

Corporate codes are part of the commercial agreement between a retailer, TMC, or agency and the carrier. The carrier communicates the applicable codes directly to the retailer. Distribusion does not hold or issue corporate codes.

Applying a corporate code

Corporate codes are applied on connections/find, submitted as cards. The name is the identifier registered for that corporate programme; the code is your negotiated account number.

 
{
  "currency": "EUR",
  "locale": "en",
  "search_bounds": [
    {
      "departure_location": { "type": "stations", "value": ["DEBERZOB"] },
      "arrival_location":   { "type": "stations", "value": ["DEMUCZOB"] },
      "departure_date": "2026-09-15"
    }
  ],
  "cards": [
    { "name": "BAHNCORPORATE", "code": "8100033" }
  ]
}

GET /cards returns the cards enabled for your account, including whether a code is required and whether the card is sent at booking or passenger level. The same card must be repeated on connections/vacancy, seats/availability and reservations/create. Carriers re-price on each call, so a code that is dropped after search returns the public fare.

Depending on how the carrier works, the response returns only corporate fares, or both public and corporate fares. Both behaviors are expected.

Identifying corporate fares

When a corporate code has been applied to a fare, the fare references it through its applied_cards relationship, and the card is returned in included. This is present whenever a carrier honours a code, so it is the signal to rely on.

​"relationships": {
    "applied_cards": {
        "data": [
            {
                "id": "BAHNCORPORATE-8100033",
                "type": "applied_cards"
            }
        ]
    }
} ​"relationships": {
    "applied_cards": {
        "data": [
            {
                "id": "BAHNCORPORATE-8100033",
                "type": "applied_cards"
            }
        ]
    }
}

Where a carrier sells its negotiated products as separate fare classes, that fare class is additionally flagged as corporate. The flag sits on the fare_classes object referenced by the fare, not on the fare itself:

​"attributes": {
    "code": "FARE-10",
    "name": "Premium Empresas",
    "journey_type": "single",
    "iata_category": "Business Class",
    "corporate": true
} ​"attributes": {
    "code": "FARE-10",
    "name": "Premium Empresas",
    "journey_type": "single",
    "iata_category": "Business Class",
    "corporate": true
}