AutoPrice / Manual Fare API Reference

POST

book/airoffer/reservationworkbench/{workbenchID}/offers/buildfromunpricedsegments

For {workbenchID} send the workbench identifier returned in ReservationResponse/Identifer/value in the workbench create response.

Base path:

Pre-production https://api.pp.travelport.net/11/air/

Production https://api.travelport.net/11/air/

Travelport has updated all JSON API authentication and authorization endpoints. The previous production endpoints will be deprecated 30 Jan 2026. Pre-production endpoints were deprecated 5 Dec 2025. See Endpoint Migration for details.

Related Content: Booking Guide

GDS only; NDC does not support unpriced segments.

Use the AutoPrice/Manual Fare API to price unpriced segments. Unpriced segments can be booked or added to an existing booking with the Unpriced Segment API. Unpriced segments are also created when the filed fare is removed from an offer with the Cancel Workbench Items API.

The AutoPrice/Manual Fare API can either:

  • auto-price one or more unpriced segments

  • manually build a fare for one or more unpriced segments using fare and pricing details from the airline or another source

Each scenario uses its own request payload.

See Unpriced Segments and AutoPrice/Manual Fares in the Booking Guide for workflow and support details on both options.

Manual fare is available only to select customers at this time. It is planned for full deployment 5 Feb 2026.

Request

As part of the request requirements, also see Authentication and Common Air Headers.

Query Parameters

None.

Request Body to Auto-price Unpriced Segment

Use the following payload to auto-price unpriced segments.

Request Body to Build Manual Fare

Use the following payload to build a manual fare for unpriced segments. Data and objects included here vary depending on the fare built, but at a minimum must include all of the following:

  • fare basis code

  • currency and fare

  • IATA ROE

  • taxes

  • total price including base price and taxes

  • fare calculation line

Optional data can include the following:

  • ticket designator

  • not valid after/not valid before

  • equivalent fare

  • stopover

  • tax exempt

  • endorsement (note that returning endorsements in the Reservation Retrieve requires requesting the detailed view)

  • baggage allowance

Object

Description

Required/Optional

OfferQueryBuildFromUnpricedSegments

Top level object.

Required

BuildfromUnpricedSegments

Top level object. Send with @type OfferQueryBuildFromUnpricedSegments.

Includes UnpricedFlightSegmentCriteria and ManualPrice.

Required

UnpricedFlightSegmentCriteria

 

Required

UnpricedFlightSegmentRefs

 

Required

Sequence

Number. Send sequence of the leg to which this fare applies.

Required

TravelerRefs

Standard TravelerRefs object. Array. Send traveler ref ids for all travelers on this fare.

Required

ManualPrice

Top level object to build the manual fare.

Required

id

String. Custom id for this manual fare.

Required

ContentSource

String. Identifies content source. Send with value GDS.

Required

PassengerFlight

Array. Send PTC and class/fare information. See the AirPrice Reference Payload API Reference response section for details, and refer to schema for full details.

Data and objects included here vary depending on the fare built; see note above for required and optional data.

Required

PriceDetail

Send price details for the manual fare in the standard Price object. See the AirPrice Reference Payload API Reference Price object table for details, and refer to schema for full details.

Data and objects included here vary depending on the fare built; see note above for required and optional data.

Required

Response

Example Request

For additional examples, download the developer toolkits and see Using Postman and Developer Toolkits.

Example Response

For additional examples, download the developer toolkits and see Using Postman and Developer Toolkits.