Breeze Revenue Booking Designator (RBD) hierarchy
Breeze uses two separate hierarchies: one for API-based channels and another used over legacy EDIFACT/TTY distribution connections.
Primary hierarchy
Section titled “Primary hierarchy”Channels
Section titled “Channels”- Breeze JSON API
- Breeze XML API (NDC)
- flybreeze.com
- pro.flybreeze.com
Economy hierarchy
Section titled “Economy hierarchy”| Economy (Y) | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Y (highest) | X | W | V | U | T | S | R | Q | P | O | N | M | L | K | J | I | H | G | F | E | D | C | B | A (lowest) |
Premium economy & business/first
Section titled “Premium economy & business/first”Breeze does not use distinct RBDs for Premium Economy or Business/first experiences in our APIs. Instead, we apply bundles or product families on top of the economy RBD.
Legacy hierarchy
Section titled “Legacy hierarchy”Bookings created through legacy channels may use a legacy booking RBD that maps to a different internal Breeze RBD. That internal RBD is selected to most closely approximate the booked class for pricing, inventory, and servicing within Breeze systems.
Channels
Section titled “Channels”- GDS (legacy EDIFACT/TTY)
- Interline (legacy EDIFACT/TTY)
- Breeze etickets (accounting code 177)
Economy hierarchy
Section titled “Economy hierarchy”| Economy (Y) | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Y (highest) | B | H | K | M | L | E | Q | T | S | V | N (lowest) |