POST/v2/fare-rules

Fare rules

Penalties and rule prose for an itinerary you already hold from search or detail.

Bearer tokenAuthority: B2C_FARE_RULEhttps://api1.vacaychi.com/booking

Use the flight id saved from search or flight detail. itineraryId is accepted as an alias of flightId. pricingIndex defaults to 0. Direct Sabre fields (fare basis, origin, destination, marketing carrier, PCC, departure time) are discarded. Sending only those fields, with no flightId, is 400.

ATPCO uses Sabre OTA Air Rules. NDC prices the stored offer and falls back to the penalties captured at search.

cURL

bash
curl -X POST https://api1.vacaychi.com/booking/v2/fare-rules \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"flightId":"66d2...","pricingIndex":0}'

Headers

Content-Typeapplication/json
required

JSON body

Request

JSON
{
  "flightId": "66d2...",
  "pricingIndex": 0
}

Body fields

flightIdstring
required

Itinerary id from search or flight detail. itineraryId is an alias.

pricingIndexnumber
optional

Which branded fare to explain. Defaults to 0.

Response

200
{
  "message": "Success",
  "data": [
    { "rph": "1", "title": "PENALTIES", "text": "CHANGES PERMITTED…" }
  ],
  "error": null
}

Response fields

rphstring

Rule paragraph number

titlestring

Rule title, such as PENALTIES

textstring

Rule prose

Errors

400flightId is required

No itinerary id

404Itinerary not found for id: …

Unknown id

400Fare rules unavailable for this NDC fare

NDC offer and stored penalties are both empty

401 / 403UNAUTHORIZED

Missing token, or the token lacks B2C_FARE_RULE