Add SeatMap

Book or assign seats to passengers for an existing booking. This endpoint allows seat selection after the initial booking has been made.

---

Endpoint

• URL: /api/v1/flight/addseatmap
• 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	Booking system code (e.g., VN, VJ, 1A)
bookingCode	string	No	Booking code (PNR)
seatMaps	array	No	List of seat assignments (see SeatMapInfo)

SeatMapInfo Object

Field	Type	Required	Description
passengerId	string	No	Passenger ID from booking retrieval
seatValue	string	No	Seat value from Get SeatMap response

Example Request:

{
  "system": "VN",
  "bookingCode": "ABC123",
  "seatMaps": [
    {
      "passengerId": "PAX001",
      "seatValue": "encoded_seat_value_from_seatmap"
    },
    {
      "passengerId": "PAX002", 
      "seatValue": "encoded_seat_value_from_seatmap"
    }
  ]
}

---

Request Constraints & Business Rules

• The booking must exist and be in a valid state for seat assignment.
• Passenger IDs must match those from the booking retrieval response.
• Seat values must be obtained from a recent Get SeatMap response.
• Seats must be available at the time of assignment.
• Premium seats may have additional charges.
• Some seats may have passenger type restrictions (e.g., emergency exit rows).
• Changes to seat assignments may be restricted based on airline policies.

---

Response Structure

Field	Type	Nullable	Description
system	string	Yes	System name (e.g., VN, VJ, 1A)
status	boolean	No	true if successful, false if failed
error	object	Yes	Error details (if any)
description	string	Yes	Error description (if any)
trackingId	string	Yes	Tracking ID for request logs
trackingTime	string	Yes	Time for request tracking (ISO 8601 format)

Error Object

Field	Type	Nullable	Description
id	integer	No	Error code ID
message	string	Yes	Error message

Example Response:

{
  "system": "VN",
  "status": true,
  "error": null,
  "description": null,
  "trackingId": "abc-123",
  "trackingTime": "2024-06-01T12:00:00Z"
}

---

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.
• Passenger IDs are validated against the booking.
• Seat values are validated for authenticity and availability.
• All seat assignment actions are logged and traceable.

---

Validation Questions

• How long are seat values valid for assignment?
• Can seats be reassigned after initial assignment?
• Are there fees for premium seat selections, and how are they handled?
• What happens if a seat becomes unavailable between selection and assignment?

---

For integration support, see Contact Support.