Get Cabin For RBD

The API uses the ATPCO RBD Answer Table to determine the cabin name for the given information. Only the first match for the given information will be returned. The more information given will result in a more accurate return. If the processing/ticketed date is not provided, the assumption will be current date.

The mandatory information is carrier code, RBD (or class code), origin and destination of the travel segment, flight number is mandatory unless this is an open segment type. Travel Date (departure date) is required unless this is an open segment type.

API Information

Target Audience
All Sabre APIs Customers
Current Version
v1.0.0
Authentication
Sessionless Token
Method/Endpoint
POST /v1.0.0/rbd/cabin

Ready to try the APIs?

Ready to get your hands dirty?

 Register Try the APIs

Ready to launch?

Ready to step up to the production level service? We're standing by to fit you for your spacesuit.

Request Production Key

Example

You can use this service to check Reservation Booking Designator (RBD) for specified market/flight/equipment at a given date.

Request

SegmentItems

object

Contains information about all segments in this request:

  • Segment or OpenSegment (max of 1024 items)
  • Version
  • Lang
Segment

array

This segment will contain flight number, carrier code, origin, destination, id, booking code and departure date.

Processing date and equipment are optional.

Segment may contain information about:

  • Carrier Code, string
  • Origin, string
  • Destination, string
  • Id, number
  • Booking code(or Class Code), string
  • Flight number, number
  • Departure date, string
  • Processing date, string
  • Equipment type, string
OpenSegment

array

This segment is an open segment and will not contain information about flight number and equipment.

Departure date and Processing date are optional. Rest of properties are required.

CarrierCode

string, required

IATA carrier code associated with the travel being validated or value 'YY' to indicate IATA Reso 728 default RBD by cabin mapping.

Sample value: AA

BookingCode

string, required

1 character class code or RBD code.

Only one value is accepted.

Sample value: C

Origin

string, required

3 character airport/city code of the travel being validated.

Sample value: DFW

Destination

string, required

3 character airport/city code of the travel being validated.

Sample value: DFW

ProcessingDate

string, optional

Date and time of the requested cabin information. It could be past date for historical, but no earlier than two years in the past.

If omitted, Processing date is current day.

Max value: “9999-12-31 23:59:59:59.999”

Sample value: 2017-12-31T23:47:18

Id

integer, required

Segment id to match with the response especially when multiple items are provided.

Sample value: 1

EquipmentType

string, optional*

IATA equipment code of the flight information.

If equipment not provided, we do not guarantee that correct cabin is returned for historical requests.

Sample value: 747

*If this is an open segment type, equipment type is not valid.

FlightNumber

short int, required*

Flight number on which this service is being processed.

If not provided may not return correct cabin.

Min value: 1

Max value: 9999

Sample value: 1234

*If this is an open segment type, flight number is not valid. Otherwise mandatory.

DepartureDate

string, required*

Departure date and time of the flight.

Max value: “9999-12-31 23:59:59:59.999”

Sample value: 2017-12-31T23:47:18

*If flight number provided, mandatory. If open segment then this is optional parameter.

Version

string, required

This is the version of the API that is being called.

Sample value: 1.0.0

Lang

string, optional

The language desired in the response for the cabin names. If not provided, default is English.

Valid options are:

  • EN (English),
  • FR (French),
  • NL (Dutch),
  • DE (German),
  • IT (Italian),
  • PT (Portuguese),
  • ES (Spanish),
  • SE (Swedish)

Sample value: EN

Response

Status

string

Returns if the call was successful or not.

Sample value: SUCCESS

SegmentItems

array

Repeats associated cabin information with related input:

  • Cabin, array
Cabin

array

Contains all information for this segment’s cabin:

  • Code, string
  • SabreCode, string
  • LongName, string
  • ShortName, string
  • SeqNo, number
  • RefId, number
Code

string

Specifies the applicable ATPCO cabin associated to RBD codes.

Sample value: F

SabreCode

string

Specifies the applicable Sabre cabin associated to RBD codes.

Sample value: S

LongName

string

The name that represents the cabin code. This has up to 20 characters.

Sample value: PREMIUM BUSINESS

ShortName

string

The 8 character name that represents the cabin code.

Sample value: PRM BUSN

SeqNo

integer

The sequence number used from the ATPCO RBD table. This can help introubleshooting.

Sample value: 100100

RefId

integer

The segment ID from the request that the cabin information relates to.

Sample value: 1

ErrorItems

array, if no errors, then null

Contains:

  • Error, array
Error

array

Contains information on each error:

  • Code, string
  • ShortDescription, string
  • LongDescription, string
Code

string

Error code.

Sample value: INVALID REQUEST

ShortDescription

string

Short description of error.

Sample value: “javax.validation.ConstraintViolation”

LongDescription

string

Long description of error.

Sample value: "origin: must match pattern [A-Z]{3}”

Version

string

Contains information which version of the service was used.

Sample value: 1.0.0

Lang

string

Contains information which language is returned in the names.

Sample value: EN

Sample request

{
  "segmentItems":{
    "segment":[
      {
        "carrierCode":"AA",
        "origin":"AAA",
        "processingDate":"2017-11-05T13:47:18",
        "destination":"AAB",
        "id":1,
        "bookingCode":"A",
        "departureDate":"2017-11-05T23:47:18",
        "equipmentType":"111",
        "flightNumber":1111
      }
    ],
    "openSegment":[
      {
        "carrierCode":"AB",
        "origin":"AAC",
        "processingDate":"2017-11-05T13:47:18",
        "destination":"AAD",
        "id":1025,
        "bookingCode":"A",
        "departureDate":"2017-11-05T23:47:18"
      }
    ]
  },
  "version":"1.0.0",
  "lang": "EN"
}

Sample response

{
  "status":"SUCCESS",
  "segmentItems":{
    "cabin":[
      {
        "code":"F",
        "sabreCode":"F",
        "longName":"FIRST",
        "shortName":"FIRST",
        "seqNo":100210,
        "refId":1
      },
      {
        "code":"Y",
        "sabreCode":"Y",
        "longName":"ECONOMY",
        "shortName":"ECONOMY",
        "seqNo":100000,
        "refId":1025
      }
    ]
  },
  "errorItems":null,
  "version":"1.0.0",
  "lang":"EN"
}

Errors

An HTTP status code is always returned. For information about the error response format, see the: Sabre APIs: errors page.

400 BAD REQUEST

Incorrect request

Request body was empty.
Requested segment and open segment contains more than one error.
Request contains max number of allowed segments to be requested (request can have 1024 segments and 1024 open segments, not more).
Request's body contains partially broken name in one of elements.

404 NOT FOUND

Incorrect request

The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.

405 METHOD NOT ALLOWED

Sending GET request

Sending request with different method than POST (example GET, PUT etc.). Accepted request method is POST.

415 UNSUPPORTED MEDIA TYPE

Incorrect media type

Request with wrong content-type parameter in header. Accepted is only 'application/json'.

500 INTERNAL SERVER ERROR

A generic error message

Given when an unexpected condition was encountered and no more specific message is suitable.

Docs Navigation