Skip to main content

Get Baggages

Retrieve available baggage options for a selected flight.


Endpoint

  • URL: /api/v1/flight/getbaggages
  • Method: POST
  • Auth Required: Yes (Bearer Token/X-api-key)
  • Content-Type: application/json

Authentication

This endpoint requires a valid JWT Bearer token in the Authorization header:

Authorization: Bearer <access_token>

Obtain tokens via /api/v1/sign-in (POST) with your credentials.


Request Structure

FieldTypeRequiredDescription
systemstringYesSystem code (e.g., VN, VJ, 1A)
flightValuestringYesEncoded flight value from Search Result
airlinestringNoAirline code (IATA 2-letter, e.g., VN, VJ, AF)

Sample Request:

{
"system": "VN",
"flightValue": "eyJmYXJlRGF0YUlkIjoxLCJvcHRpb25JZCI6MCwiZmxpZ2h0SWQiOjAsImxlZyI6MCwiYWlybGluZSI6IlZOIiwg...",
"airline": "VN"
}

Request Constraints & Business Rules

  • Before booking, system and flightValue must match the values from the Search Flight response.
  • After booking or after ticket issuance, use the latest flightValue from the Retrieve Booking response. This ensures the most up-to-date and valid flight context.
  • Do not reuse an old flightValue if the booking itinerary has changed.
  • airline must be a valid IATA code for the selected flight.
  • Only available after a successful flight search.

Response Structure

FieldTypeNullableDescription
systemstringYesName of the airline system
statusbooleanNotrue if successful, false if failed
errorErrorCode (object)YesError details (if any)
descriptionstringYesError description (if any)
trackingIdstringYesTracking ID for request logs
trackingTimestring (date-time)YesTime for request tracking
baggagesarray of BaggageYesList of available baggage options

Baggage Object

FieldTypeNullableDescription
codestringYesBaggage code
namestringYesBaggage name (e.g., 25kg, 30kg)
routestringYesRoute the baggage applies to (e.g., HANSGN)
pricesarray of PriceBaggageTypeYesPrice details for each passenger type

PriceBaggageType Object

FieldTypeNullableDescription
passengerIdstringYesPassenger ID (for post-booking queries)
passengerTypestringYesPassenger type (ADT, CHD, INF)
pricenumberNoTotal price for this passenger type
currencystringYesCurrency (e.g., VND, USD)
valuestringYesEncoded baggage value

Sample Response

{
"system": "VN",
"ancillaries": [],
"baggages": [
{
"code": "ABAG",
"name": "23KG",
"route": "SGNDAD",
"prices": [
{
"passengerId": "0",
"passengerType": "ADT",
"price": 324000,
"currency": "VND",
"value": "/GOg904J3bYNoyfIH+INiseAoQoA/JwZSEV38KxOzNJY1/q+1y1UnsrnH3A..."
}
]
}
],
"status": true,
"error": null,
"description": null,
"trackingId": "abc123",
"trackingTime": "2025-07-01T08:18:01.2638496+00:00"
}

Baggage & Price Structure

  • Each baggage option represents an add-on (e.g., 25kg, 30kg) that can be purchased for the selected flight.
  • The prices array lists the cost for each passenger type (ADT, CHD, INF). The value field is an encoded object used for subsequent booking or add-baggage requests.

Error Codes

This endpoint may return the following error codes:

For a complete list of error codes, see Error Codes.


Security & Validation

  • All input is validated for type and required fields.
  • Only authenticated users can access this endpoint.
  • The endpoint is protected against tampering with flightValue and airline.

Validation Questions

  • Are there any restrictions on which baggage options can be combined?
  • Is the value field always required for subsequent add-baggage requests?
  • Are there time limits for when baggage can be added before departure?

For integration support, see Contact Support.