A null PublishedFare means the flight-search response did not provide a value in that field for the selected result. It is not the same as a fare of zero. Do not replace it with another fare field unless the API documentation for your integration defines that mapping.
Checks to make
- Compare the supplier response with the response returned by your integration. If the supplier payload already has a null value, confirm the fare rules and supported itinerary with the supplier.
- Make sure you are reading the fare for the same search result and result identifier returned by the latest search. Repeat the search if the result may have expired.
- Check the response parser and field mapping. Handle an absent or null value separately from numeric zero, and do not infer a payable amount from a different field.
- Compare a result that works with one that does not, including itinerary, passenger mix, fare type and supplier. This can show whether the difference comes from the provider response or your mapping.
If the source response contains a fare but your application returns null, review the parser and mapping. If the source response is already null, ask the supplier whether that result should include a published fare. Before sharing logs with support, remove credentials, access tokens, passenger details and booking references.