Transaction and Trace IDs
Many of the Air APIs support transaction and trace IDs for both GDS and NDC content:
- For the APIs listed below, responses that return always returns a system-generated transaction ID unique to that response (transactionId).
- In addition, you can send a custom trace ID value in the message request header for any transaction. If sent, that trace ID is returned in the response (traceId).
These IDs can be used to assist in tracking and troubleshooting if you need Support Options.
Supporting APIs
All v11 versions of these APIs support trace and transaction IDs:
- Search, Next Leg Search, and Flight Specific Search
- AirPrice
- AirReservation
- Ancillary shop, price, and book
- Seats
- AirTicketing
- Exchange APIs
Trace IDs in the Request
You can send any custom trace ID value of your choice to assist in tracking. To send a trace ID, send a value in the TraceId field of the message request header of any of the APIs listed above. For more about headers, see Common Air Headers.
IDs in the Response
The APIs listed above return a transactionId object in the top level object of the response (that object name varies by API). This system-generated ID is unique for every transaction. The transaction ID is also returned in the E2ETrackingID field in the response header.
If you sent a trace ID, a traceId object with that value is also returned at the top of the response. If you did not send a trace ID in the header, traceId is not returned.
The following example shows the transaction and trace IDs as returned in different APIs.
{
"CatalogOfferingsResponse": {
"transactionId": "961x243a-1d4a-3386-a5b1-51134292f081",
"traceId": "TEST_AB",
"CatalogOfferings": { ...
{
"OfferListResponse": {
"transactionId": "330a242c-2d9a-4955-a5b1-60924253e076",
"traceId": "29110e39-c5bf-4fbb-9b5f-4d7756fc4879",
"OfferID": [
{...