Enhanced Air Ticket
Orchestrated APIs bundle several functions and operations into a single API call thus maximizing development efforts, and providing operational efficiencies by calling multiple services to fulfill a desired workflow. Features in the Orchestrated Air Ticket API include:
- Provides the capability to issue multiple Air Tickets and EMDs into a single call
- Issues multiple PQRs in one call
- Issues more than one PTC in the same transaction with installments
- Integrates printer address designation/un-designation
- Manages sessions on behalf of the client application
- Introduces error handling to ensure the successful issuance of an Air Ticket
- Returns newly issued ticket numbers together with additional details pertaining to specific documents
- Handles Context change/AAA
- Deletes air accounting lines prior to ticketing
API Information
- Target Audience
- All Sabre APIs Customers
- Current Version
- v1.2.0
- Authentication
- Sessionless Token
- Methods/Endpoints
- POST /v1.2.0/air/ticket
Ready to try the APIs?
Ready to launch?
Ready to step up to the production level service? We're standing by to fit you for your spacesuit.
Request Production KeyResources
- Orchestrated Sabre APIs® User Guide
- Release Notes
- v1.2.0 Request Schema
- v1.2.0 Request Descriptions
- v1.2.0 Response Schema
- v1.2.0 Response Descriptions
- v1.2.0 Schema common types
- v1.2.0 STL Message Payload types
- v1.2.0 STL Message Common types
Request
Request headers
- Content-Type
- required
- Valid value:
Content-Type: application/json
- Accept-Encoding
- optional
- To reduce network latency for large responses, request a compressed response. Include the "Accept-Encoding" HTTP header field in the request.
- Valid value:
Accept-Encoding: gzip
Overall response links
- Links
- array
- self
- object
- Returns the URL of the request that generated the response
- linkTemplate
- Formats an API request with placeholders for required and optional query parameters
Sample request
https://api.havail.sabre.com/v1.2.0/air/ticket
{ "AirTicketRQ": { "DesignatePrinter": { "Profile": { "Number": 1 } }, "Itinerary": { "ID": "VWKJJT" }, "Ticketing": [{ "FOP_Qualifiers": { "BSP_Ticketing": { "MultipleFOP": { "Fare": { "Amount": "100.00" }, "FOP_One": { "CC_Info": { "Suppress": true, "PaymentCard": { "Code": "VI", "ExpireDate": "2016-11", "ExtendedPayment": 12, "Number": 573912345621003 } } }, "FOP_Two": { "Type": "CK" } } } }, "PricingQualifiers": { "PriceQuote": [{ "Record": [{ "Number": 1, "Reissue": true }] }] } }, { "FOP_Qualifiers": { "BSP_Ticketing": { "MultipleFOP": { "Fare": { "Amount": "100.00" }, "FOP_One": { "CC_Info": { "Suppress": true, "PaymentCard": { "Code": "VI", "ExpireDate": "2016-11", "ExtendedPayment": 12, "Number": 443212345621003 } } }, "FOP_Two": { "Type": "CA" } } } }, "PricingQualifiers": { "PriceQuote": [{ "Record": [{ "Number": 2, "Reissue": true }] }] } }], "PostProcessing": { "EndTransaction": { "Source": { "ReceivedFrom": "SPTEST" } } } } }
Sample response
{ "AirTicketRS": { "ApplicationResults": { "status": "Complete", "Success": [{ "timeStamp": "2017-11-09T03:51:57.808-06:00" }] }, "Summary": [{ "DocumentNumber": "0017015583520", "LocalIssueDateTime": "2017-11-09T00:00:00", "DocumentType": "TKT", "IssuingLocation": "G7HE", "Reservation": { "content": "EMLRJT" }, "FirstName": "ADAM", "LastName": "JONES", "TotalAmount": { "currencyCode": "USD", "decimalPlace": 2, "content": "2078.40" } }, { "DocumentNumber": "0017015583521", "LocalIssueDateTime": "2017-11-09T00:00:00", "DocumentType": "TKT", "IssuingLocation": "G7HE", "Reservation": { "content": "EMLRJT" }, "FirstName": "MARY", "LastName": "JONES", "TotalAmount": { "currencyCode": "USD", "decimalPlace": 2, "content": "2078.40" } }] }, "Links": [{ "rel": "self", "href": "https://api.test.sabre.com/v1.2.0/air/ticket?mode=create" }, { "rel": "linkTemplate", "href": "https://api.test.sabre.com//air/ticket?mode= " }] }
Errors
An HTTP status code is always returned.
Errors that are specific to this API follow. For information about the error response format, see the: Sabre APIs: common errors page.
404 NOT_FOUND
- No results were found
- The service cannot find data to fulfill the parameters in the request. For example, there is no data available for the dates specified.
400 BAD REQUEST
- The request was not valid.
- The service does not support the data used in the request. For example, origin or destination in the request is not a valid IATA airport code.
If you receive this error:
{ status: "NotProcessed" type: "Validation" errorCode: "ERR.2SG.CLIENT.INVALID_REQUEST" timeStamp: "2016-07-19T11:43:34.599-05:00" message: "Request is invalid: Request payload is missing or it is not supported by the requested service" }
Ensure you:
- have specified a content type header with a value of 'application/json'
- are sending a JSON document in the HTTP POST's request body