Baggage API

Baggage API

Free checked, cabin and personal-item allowances for a flight, by airline, route, date, cabin, fare family, booking class and passenger type. Every answer comes from the airline's own published policy and links to the page it came from.

Base URL
https://beggage.innsightmap.com
Format
JSON, UTF-8
Authentication
None for the endpoints on this page
Version
/v1

Quick start

Ask for one flight. Send the fare family or booking class from your fare quote so the API can return a single allowance instead of every fare family on the route.

Request
curl "https://beggage.innsightmap.com/v1/baggage/info?airline=EK&origin=DAC&destination=DXB&date=2026-10-01&cabin=economy&fare_family=saver&passengers=adult,infant"
Response (shortened)
{
  "segments": [{
    "index": 0, "airline": "EK", "origin": "DAC", "destination": "DXB",
    "date": "2026-10-01", "cabin": "economy", "fare_family": "saver",
    "passengers": [{
      "type": "adult",
      "baggage": {
        "checked": { "status": "resolved", "result": { "rule_id": 708,
          "allowance": { "concept": "weight", "total_weight_kg": 25, "weight_per_piece_kg": 32,
                         "code": "25K", "text": "25 kg total, max 32 kg per bag (max 203 cm linear)" } } },
        "cabin":   { "status": "resolved", "result": { "rule_id": 743,
          "allowance": { "concept": "piece", "pieces": 1, "weight_per_piece_kg": 7,
                         "code": "1PC", "text": "1 x 7 kg (55 x 38 x 22 cm)" } } },
        "personal_item": { "status": "not_found", "note": "No published rule for this baggage type on this route." }
      }
    }, {
      "type": "infant",
      "baggage": { "checked": { "status": "resolved", "result": { "allowance": { "code": "10K", "text": "10 kg total" } } } }
    }]
  }],
  "warnings": [],
  "generated_at": "2026-09-24T14:33:00Z"
}

Try it

Runs GET /v1/baggage/info against this server with live data.

Passengers

Pick a flight and select Get allowance.

Baggage info

GET/v1/baggage/info
POST/v1/baggage/info

The endpoint to use in a booking flow. For each segment and each passenger type it returns one answer per baggage type: the allowance, or the options when the request doesn't say enough to choose one.

Use GET for one segment and POST for an itinerary of up to 16 segments.

Segment fields

Query parameters on GET, fields of each segments[] item on POST.

FieldTypeDescription
airline requiredstring2-character IATA code of the operating airline, e.g. EK.
origin requiredstring3-letter IATA airport code.
destination requiredstring3-letter IATA airport code.
dateYYYY-MM-DDTravel date. Default: today (UTC). Policies with a start or end date are applied for this day.
cabinstringeconomy, premium_economy, business, first.
fare_familystringBranded fare name, case-insensitive. The airline's own spellings and codes are accepted, e.g. EcoFly or Economy Saver.
booking_classstringOne-letter RBD, e.g. T. Used by airlines that set allowances by booking class.
ff_tierstringFrequent-flyer tier, e.g. gold. Tier additions are returned in extras. On POST a segment value overrides the top-level one.

Request-level fields

FieldTypeDescription
passengerslistadult, child, infant. Default: adult. GET: comma-separated. Duplicates are ignored; send each type once, not once per traveller.
includelistBaggage types to answer. Default: checked, cabin, personal_item. all returns every type (excess charges, sports equipment, pets and so on). GET: comma-separated.
ff_tierstringPOST only: default tier for every segment.
segments requiredlistPOST only: 1 to 16 segments in travel order.

Itinerary request

POST /v1/baggage/info
curl -X POST "https://beggage.innsightmap.com/v1/baggage/info" \
  -H "Content-Type: application/json" \
  -d '{
    "passengers": ["adult", "child", "infant"],
    "include": ["checked", "cabin"],
    "segments": [
      {"airline": "TK", "origin": "DAC", "destination": "IST", "date": "2026-11-02",
       "cabin": "economy", "fare_family": "EcoFly"},
      {"airline": "BA", "origin": "IST", "destination": "LHR", "date": "2026-11-03",
       "cabin": "economy"}
    ]
  }'

POST requires Content-Type: application/json and rejects unknown fields. The body limit is 1 MB.

Answer status

Every segments[i].passengers[j].baggage.<type> is an answer with one of three statuses.

StatusMeaningWhat to do
resolvedOne allowance applies, in result. Also used when several fare families or cabins match but all give the same bags; note says so.Show result.allowance.
multipleThe allowance depends on the cabin, fare family or booking class, and the request didn't pin it down. options lists each variant; note names the field to send.Send that field from the fare quote and ask again, or show the options.
not_foundNo published rule for this baggage type on this route.Show "not available" and fall back to the airline's fare rules.
A multiple answer: BA IST to LHR, economy, no fare family
"checked": {
  "status": "multiple",
  "options": [
    { "rule_id": 5012, "cabin": "economy", "fare_family": "basic",
      "allowance": { "concept": "piece", "pieces": 0, "code": "0PC", "text": "No allowance" } },
    { "rule_id": 5013, "cabin": "economy", "fare_family": "standard",
      "allowance": { "concept": "piece", "pieces": 1, "weight_per_piece_kg": 23,
                     "dimensions": { "length_cm": 90, "width_cm": 75, "height_cm": 43 },
                     "code": "1PC", "text": "1 x 23 kg (90 x 75 x 43 cm)" } }
  ],
  "note": "Allowance depends on the fare family; send fare_family to get one answer."
}

Rule IDs in examples are illustrative; they change when an airline's data is re-imported.

Response

FieldDescription
segments[]One per request segment, same order, with index and the normalized segment fields (codes upper-case, fare family lower-case, date filled in).
segments[].passengers[]One per requested passenger type: type and baggage, an object keyed by baggage type.
baggage.<type>.statusresolved, multiple or not_found.
baggage.<type>.resultAn allowance entry when resolved.
baggage.<type>.options[]Allowance entries when multiple.
baggage.<type>.extras[]Frequent-flyer tier additions for ff_tier, on top of the base allowance. Present with any status.
baggage.<type>.notePlain-language explanation, when there is one.
warnings[]Journey-level notes: more than one airline in the itinerary, or rules not re-verified recently.
generated_atUTC timestamp of the response.

Airlines

GET/v1/airlines
GET/v1/airlines/{iata}

The airlines in the database. An airline listed here may still have routes without published rules; the answer status tells you per request.

GET /v1/airlines
{
  "airlines": [{
    "id": 6, "iata": "BA", "icao": "BAW", "name": "British Airways", "country_code": "GB",
    "website": "https://www.britishairways.com", "official_domains": ["britishairways.com", "ba.com"],
    "alliance": "oneworld", "active": true, "last_researched_at": "..."
  }]
}

/v1/airlines/{iata} returns one airline object, or 404 airline not found.

Rules and history

GET/v1/rules/{id}
GET/v1/rules/{id}/history

One rule by the rule_id from an answer, and every reviewed version of it as {"versions": [...]}. Use this to show a customer why an allowance was quoted, or to see when an airline changed a policy.

Only reviewed data is public: published and superseded versions. A rule still in review returns 404.

Health check

GET/healthz

200 {"status":"ok"} when the database is reachable, 503 {"error":"database unavailable"} when it isn't.

Response objects

Allowance entry

What Baggage info returns in result, options and extras.

FieldDescription
rule_idThe rule this answer came from. Look it up with /v1/rules/{id}.
passenger_typeThe rule's passenger type. adult on a child request means the child gets the adult allowance (the airline has no separate child rule).
cabinCabin the rule is for, or null for all cabins.
fare_familyFare family the rule is for, or empty for all.
booking_classesRBDs the rule is for, or empty for all.
ff_tierTier, only on entries in extras.
allowanceSee below.
summaryOne line in plain language, e.g. "25 kg total, no bag over 32 kg".
conditions, notesLonger conditions from the airline's page; notes can include the evidence quote.
charges[]Prices, mainly on excess and additional: description, amount, currency (ISO 4217), unit, weight_from_kg, weight_to_kg, applies_to.
routeHow specifically the route matched, origin then destination: any, zone, country or airport, e.g. country-airport.
quality, confidenceResearch quality (confirmed, partial, needs_review, conflicting) and a 0–1 score.
sourceurl, title and is_official of the airline page the rule was taken from.
last_verified_at, staleWhen the source was last confirmed unchanged, and whether that was too long ago (30 days by default).

Allowance

FieldDescription
conceptpiece (a number of bags), weight (a total in kg) or not_applicable (information only, e.g. pet rules).
piecesNumber of bags. 0 means no allowance.
weight_per_piece_kgMaximum weight of each bag.
total_weight_kgTotal weight across all bags.
dimensionslength_cm, width_cm, height_cm and/or linear_cm (L+W+H), when the airline states them.
codeGDS-style shorthand: 2PC, 25K, 0PC. Empty when there is no number to show.
textReady to display, e.g. "2 x 23 kg" or "30 kg total, max 32 kg per bag".

Fields without a value are left out of the allowance. Read numbers from the structured fields; use code and text for display only.

Allowed values

FieldValues
cabineconomy premium_economy business first
passenger typeadult child infant
baggage typechecked cabin personal_item excess additional special sports_equipment infant_equipment oversized musical_instrument mobility_equipment medical_equipment pet interline_codeshare
allowance conceptpiece weight not_applicable
qualityconfirmed partial needs_review conflicting
charge unitper_kg per_piece per_bag flat per_segment other

Inputs are case-insensitive and trimmed. excess is the price of going over the allowance at the airport; additional is extra baggage bought in advance.

How rules are matched

Each side of a route scores any 0, zone 1, country 2, airport 3. For each baggage type the most specific rule wins, so a Dhaka–Dubai exception replaces the airline's worldwide default instead of appearing next to it. Two-way rules also match the reversed route.

A rule for the passenger's own booking class beats any generic rule, because airlines state class rules for every route. Zones are the airline's own regions, e.g. Emirates' "Indian Subcontinent".

When you leave out the cabin or fare family, every variant at the best route level comes back, and Baggage info reports them as multiple. The API never guesses a fare family.

Only rules valid on the travel date and approved by a reviewer are served. When an airline announces a change in advance, requests dated after the change get the new allowance.

Errors

Errors are JSON with one field. On POST, a problem with one segment names it, e.g. segments[1]: date must be YYYY-MM-DD; nothing is resolved until every segment is valid.

{ "error": "segments[0]: unknown airport XXX" }
StatusWhenExample message
400Missing or invalid field, invalid JSON, no segments, more than 16 segmentsorigin and destination must be 3-letter IATA airport codes
404Unknown airline or airport, rule not found or not publicsegments[0]: unknown airline ZZ
415POST without Content-Type: application/jsonContent-Type must be application/json
500Server error; details are logged, not returnedinternal error
503Health check: database unreachabledatabase unavailable

A route with no published rule is not an error: it returns 200 with not_found answers.

Integration guidelines

Send what the fare quote knows

Pass cabin and fare_family (the brand name from NDC or GDS branded fares), and booking_class when you have it. Without them most airlines return multiple.

Query the operating airline per segment

Send one segment per flight with the operating carrier's code. For mixed-airline tickets the API returns each airline's allowance and a warning: under IATA Resolution 302 the most significant carrier's rules usually cover the whole ticket, so confirm against the fare's baggage (e.g. the GDS baggage text) before showing a single journey allowance.

Prefer the airline's own answer when you have one

When the PNR, ticket or NDC offer states a free baggage allowance, that is binding for the passenger; use this API to fill gaps, explain the allowance, and add cabin bag, personal item and dimensions that fare data rarely carries.

Handle every status

Show resolved as is, show the options or ask again on multiple, and show "not available" on not_found. Don't treat not_found as zero bags.

Store the rule ID with the booking

Save rule_id and generated_at with what you showed the customer. /v1/rules/{id}/history can later prove what the policy was on that day. Don't hard-code rule IDs: new versions get new IDs.

Cache lightly

Responses are cached on the server for 6 hours and the cache is cleared when an airline's rules change. Caching on your side for up to an hour is fine; don't keep answers for days.

Link the source

Show source.url as "Airline baggage policy" next to the allowance, and treat stale: true or a quality other than confirmed as "check with the airline".

The public endpoints have no API key or rate limit yet. Before production traffic from partners, keys and per-client limits will be added; requests will then need an Authorization header. The request and response formats on this page won't change.

Versioning

Everything is under /v1. Within v1, fields and baggage types may be added, so ignore fields you don't know. Removing or renaming a field, or changing its meaning, would come as /v2 with /v1 kept running alongside.

Machine-readable description: /openapi.yaml (OpenAPI 3.0), for Postman, Insomnia or code generators.