Flight itinerary

What this Offering represents

The IF123-2026-09-14-SFO-JFK Offering represents InFlow Air flight 123 from San Francisco to New York on September 14, 2026, in economy cabin. It does not represent every flight between the two cities or every departure operated under flight number 123.

{
  "odp_version": "1.0",
  "id": "IF123-2026-09-14-SFO-JFK",
  "name": "InFlow Air 123 from San Francisco to New York",
  "description": "A nonstop scheduled flight offered in economy cabin.",
  "web_url": "/flights/IF123-2026-09-14-SFO-JFK",
  "price": {
    "type": "starting_at",
    "amount": "199.00",
    "currency": "USD"
  },
  "schema": {
    "url": "https://travel.example/schemas/flight-itinerary-1.json"
  },
  "attributes": {
    "operating_carrier": "IF",
    "flight_number": "123",
    "departure": {
      "airport": "SFO",
      "scheduled_at": "2026-09-14T08:30:00-07:00",
      "terminal": "1"
    },
    "arrival": {
      "airport": "JFK",
      "scheduled_at": "2026-09-14T17:05:00-04:00",
      "terminal": "5"
    },
    "cabin": "economy",
    "included_checked_bags": 1,
    "refundable": false
  },
  "actions": [
    {
      "id": "request-quote",
      "rel": "quote",
      "description": "Request current traveler-specific availability, fare, taxes, and conditions.",
      "openapi": {
        "url": "https://travel.example/openapi.json",
        "operation_id": "createFlightQuote"
      },
      "authentication": "required"
    }
  ]
}

Identify each scheduled itinerary

Publish another Offering when a departure, cabin, or other choice can be independently retrieved, quoted, reserved, or purchased. This lets an Agent select an exact itinerary before it chooses an Action.

Preserve places and local times

The departure and arrival objects keep each airport together with its scheduled time and optional terminal. The Attribute Schema constrains airport values to three-letter International Air Transport Association location codes and requires each scheduled time to use the JSON Schema date-time format.

The UTC offsets are part of the scheduled values. An Agent preserves them when displaying or comparing the itinerary rather than treating both clock readings as if they used the same offset.

Describe the flight

ODP does not define airline-specific fields. The Service's Attribute Schema defines this Offering's carrier, flight number, departure, arrival, cabin, baggage, and refundability fields. Another travel Service can use a different schema for its own catalog.

An Agent should validate the attributes against this schema before relying on them. If the schema is unavailable, invalid, unsupported, or does not match the attributes, the Agent treats the attributes as uninterpretable while retaining the Offering's identity, description, Price Preview, web page, and Actions.

Qualify baggage and refundability

The baggage count and refundability flag describe the fare presented during discovery. They are not universal promises for every traveler. Loyalty status, traveler type, route rules, or a different available fare can affect the terms returned by the quote operation.

An Agent presents these values with the Offering and uses the later quote for the terms that apply to the traveler's request. It must not convert refundable: false into a broader statement that the flight has no refundable fares.

Present a starting price

The starting_at Price Preview states that the lowest advertised starting price is 199.00 USD. It helps an Agent compare the itinerary during discovery, but it does not promise that this fare remains available for a particular traveler.

Request a traveler-specific quote

The request-quote Action identifies the createFlightQuote operation in an OpenAPI 3.1 document. OpenAPI is appropriate here because traveler inputs, availability, fare details, taxes, conditions, and the response structure require a fuller interface description than a compact Action target provides.

The example OpenAPI URL is illustrative. A deployed Service must publish an OpenAPI 3.1 document containing exactly one operation whose operationId is createFlightQuote. An Agent does not guess another operation if that lookup fails or is ambiguous. It interprets a successful quote response according to that OpenAPI operation, not as an ODP Offering response.

Retrieve OpenAPI without credentials

An Agent retrieves the OpenAPI document anonymously. It must not attach AEP credentials, payment credentials, cookies, or authorization copied from the Offering request. The document describes the quote operation, but it is not itself a request to quote or book the itinerary.

If the document is unavailable or invalid, or the operation ID cannot be resolved exactly once, only this Action becomes unusable. The itinerary's identity, description, Price Preview, web page, and interpretable attributes remain available.

Authenticate before requesting terms

authentication: required tells the Agent that the quote operation cannot succeed anonymously. It does not select an authentication protocol or provide credentials. The Agent begins the quote request in its current authentication context, follows any live authentication challenge, and uses only credentials valid for that Service.

Follow discovery to quote

The advertised ODP path ends with current terms. It does not imply that the traveler approved a booking or purchase.

Keep booking outside ODP

ODP publishes the itinerary and identifies how to request a quote. The travel Service owns live availability, traveler validation, fare rules, taxes, seat selection, reservations, payment, ticketing, check-in, changes, cancellations, and disruption handling.

A successful quote does not reserve a seat, create a booking, issue a ticket, or authorize payment. Those effects require separate Service operations and explicit caller decisions.

Inspect the example artifacts

The carrier, domains, schedule, and fare are illustrative. A deployed Service supplies current Offerings and hosts every referenced schema, web page, OpenAPI document, and Action target.

• Generated example: open the published flight itinerary example and its source files
• Full Offering: inspect the scheduled itinerary, travel attributes, Price Preview, and quote Action
• Attribute Schema: inspect the travel field definitions and validation constraints

Next steps