Delete SeatMap

Cancel or remove seat assignments from passengers for an existing booking. This endpoint allows removal of previously assigned seats.

---

Endpoint

• URL: /api/v1/flight/deleteseatmap
• 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 to remove (see SeatMapInfo)

SeatMapInfo Object

Field	Type	Required	Description
passengerId	string	No	Passenger ID from booking retrieval
seatValue	string	No	Seat value of the assigned seat to remove

Example Request:

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

---

Request Constraints & Business Rules

• The booking must exist and have existing seat assignments.
• Passenger IDs must match those from the booking retrieval response.
• Seat values must match currently assigned seats for the passengers.
• Some airlines may not allow seat removal after certain conditions (e.g., within 24 hours of departure).
• Premium seat fees may or may not be refundable depending on airline policy.
• Seat removal may affect other passengers' seating arrangements in group bookings.

---

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 assignments are verified before removal.
• All seat removal actions are logged and traceable.

---

Validation Questions

• Are there time restrictions for removing seat assignments?
• How are refunds handled for premium seat fees?
• What happens to group seating arrangements when seats are removed?
• Can seat assignments be removed after check-in has occurred?

---

For integration support, see Contact Support.