Retrieve and apply ATPCO fare rules (CAT 15 sales restrictions) before ticketing in an Amadeus flow

This API has logged drift

Steps

1. After a Flight Offers Search, select the chosen offer and call POST /v1/shopping/flight-offers/pricing with the full offer and include=detailed-fare-rules as a query parameter — there is no separate /v1/shopping/airTraffic/fares endpoint; fare rules are only surfaced through this pricing call.
2. Parse each traveler's fareDetailsBySegment[].fareRules.rules[] array; each rule is a TermAndCondition object limited to category REFUND, EXCHANGE, REVALIDATION, REISSUE, REBOOK, or CANCELLATION, plus circumstances, notApplicable, maxPenaltyAmount, and a descriptions[] array of free-text blocks.
3. Traditional ATPCO CAT 15 content (advance-purchase requirements, blackout dates, point-of-sale/channel restrictions) is not exposed as its own structured category in the Self-Service fare-rules response; look for it inside descriptions[].text on the applicable rule rather than a dedicated field.
4. Cross-check any advance-purchase or point-of-sale restriction you find in the free text against the booking channel and market before proceeding, since Self-Service does not guarantee complete ATPCO rule text in every market.
5. Surface any restriction you can actually confirm (fee amount, deadline, applicability) to the traveler in plain language before ticketing; do not claim a CAT 15 sales restriction was checked if the text wasn't present in the response.
6. If your product requires guaranteed, comprehensive ATPCO CAT 15 sales-restriction data rather than best-effort text embedded in refund/exchange/cancellation rules, that level of coverage is an Amadeus Enterprise API capability, not Self-Service.