Guides · Quality Scores

Quality Scores

Every offer from POST /v1/shopping/offers (and its stream) carries quality_score, from 0.0 to 1.0: how complete the offer's data is.

D-233
0.00.51.0SCOREquality_score0.0 to 1.0: how completeBooking fieldsWeigh the mostDisplay fieldsWeigh the leastMissing fieldNever filled with a guessChecked bagIncluding one counts too

What it measures

The share of the offer's fields that are present, weighted by importance: fields a booking needs count most, display-only fields least. Every slice and flight is checked.

Including a checked bag also counts, so a complete fare without one scores just below 1.0. Missing data is never filled with a guess.

quality_score: 0.0 … 1.0
1.0 = every field the score looks at is present
< 1.0 = some of those fields are missing or empty

What it is not

  • Not a booking guarantee: a complete offer can still expire or be refused at pricing.
  • Not a measure of price or value. Results are sorted by price, not by score.
  • Not fixed across releases: revisit any threshold you set.

How to use it

  • Filter out low scores (e.g. < 0.5) in automated booking.
  • Sort or badge offers by completeness in your UI.
Offer Quality Scores: How Norba Rates Airline Data | Docs