Update Passenger

Update passenger information for an existing booking. This endpoint allows you to modify passenger details such as name, contact information, documents, and membership details.

---

Endpoint

• URL: /api/v1/flight/updatepassenger
• 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)
passengers	array	No	List of passengers to update (see PaxInfo)

PaxInfo Object

See PaxInfo for complete passenger information structure including:

• Basic passenger details (name, gender, birth date)
• Contact information (email, phone)
• Document information (passport, ID)
• Membership details (frequent flyer programs)

Example Request:

{
  "system": "VN",
  "bookingCode": "ABC123",
  "passengers": [
    {
      "index": 1,
      "passengerId": "PAX001",
      "passengerType": "ADT",
      "title": "MR",
      "gender": true,
      "givenName": "JOHN",
      "surname": "SMITH",
      "dateOfBirth": "1990-01-01",
      "email": "john.smith@example.com",
      "phone": "+84901234567",
      "document": {
        "type": "P",
        "number": "A1234567",
        "issueCountry": "US",
        "issueDate": "2020-01-01",
        "expiryDate": "2030-01-01"
      }
    }
  ]
}

---

Request Constraints & Business Rules

• Only bookings that exist and are eligible for update can have passenger information modified.
• The bookingCode must match an existing booking.
• Passenger updates may be restricted based on booking status (e.g., after ticketing).
• Name changes may require additional validation or fees depending on airline policy.
• Document information must be valid and meet airline requirements.
• All changes are auditable via trackingId and trackingTime.

---

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 information is validated against airline requirements.
• Document information is validated for format and expiry dates.
• All actions are logged and traceable.

---

Validation Questions

• What passenger information can be updated after booking vs. after ticketing?
• Are there restrictions on name changes (spelling corrections vs. complete name changes)?
• What document types are accepted for different passenger types?
• How are validation errors handled for individual passengers in a multi-passenger update?

---

For integration support, see Contact Support.