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

Field	Type	Required	Description
system	string	No	System code (e.g., VN, VJ, 1A)
flightValue	string	No	Encoded flight value from Search Result
airline	string	No	Airline code (IATA 2-letter, e.g., VN, VJ, AF)

Example Request:

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

---

Request Constraints & Business Rules

• system and flightValue must match the values from the flight search response.
• If you want to add baggages to an existing booking, you should use the flightValue from the Retrieve Booking API response as the flightValue in the get baggages API request. This ensures the most up-to-date and valid flight context.
• airline must be a valid IATA code for the selected flight.
• Only available after a successful flight search.

---

Response Structure

Field	Type	Nullable	Description
system	string	Yes	Name of the airline system
status	boolean	No	true if successful, false if failed
error	ErrorCode (object)	Yes	Error details (if any)
description	string	Yes	Error description (if any)
trackingId	string	Yes	Tracking ID for request logs
trackingTime	string (date-time)	Yes	Time for request tracking
baggages	array of Baggage	Yes	List of available baggage options

Baggage Object

Field	Type	Nullable	Description
code	string	Yes	Baggage code
name	string	Yes	Baggage name (e.g., 25kg, 30kg)
route	string	Yes	Route the baggage applies to (e.g., HANSGN)
prices	array of PriceBaggageType	Yes	Price details for each passenger type

PriceBaggageType Object

Field	Type	Nullable	Description
passengerId	string	Yes	Passenger ID (for post-booking queries)
passengerType	string	Yes	Passenger type (ADT, CHD, INF)
price	number	No	Total price for this passenger type
currency	string	Yes	Currency (e.g., VND, USD)
value	string	Yes	Encoded baggage value

---

Example 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

See Error Codes for details on possible error responses.

---

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.