Delete Ancillary

Remove one or more ancillary services from an existing booking.

---

Endpoint

• URL: /api/v1/flight/deleteancillary
• 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	Yes	Booking system code (e.g., VN, VJ, 1A)
bookingCode	string	Yes	Booking code (PNR)
services	array of ServiceInfo	Yes	List of ancillary services to remove

ServiceInfo Object

Field	Type	Required	Description
quantity	integer	Yes	Number of units to remove
ancillaryValue	string	Yes	Encoded ancillary value from getancillaries

Example Request:

{
  "system": "VN",
  "bookingCode": "ABC123",
  "services": [
    {
      "quantity": 1,
      "ancillaryValue": "eyJ2YWx1ZSI6ICJNRUFMIiwgInByaWNlIjogMTUwMDAwfQ=="
    }
  ]
}

---

Request Constraints & Business Rules

• bookingCode must refer to an existing, valid booking.
• services must use ancillaryValue from a valid getancillaries response.
• Only ancillaries that have been added to the booking can be removed.
• Some ancillaries may have time or quantity restrictions for removal.

---

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

Example Response:

{
  "system": "VN",
  "status": true,
  "error": null,
  "description": null,
  "trackingId": "abc123",
  "trackingTime": "2025-07-01T07:05:00.000Z"
}

---

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 ancillaryValue and bookingCode.

---

Validation Questions

• Are there limits on the number or type of ancillaries that can be removed per booking?
• Is there a time window before departure when ancillaries can no longer be removed?

---

For integration support, see Contact Support.