{"introduction":"This document provides a reference for both query and response for the BI Transactions API version 1.0. It includes a series of notes and instructions that outline the BI Transactions API version 1. The API provides users with a simple, standardised, resource-oriented, RESTful interface with JSON-formatted responses that make it easy to fetch, filter and retrieve Transaction data. To have a secure data transfer and streamlined integration, we use the HTTPs protocol for API calls.","audience":{"label":"Audience","description":"This document is aimed for The BI Transactions API customers, partners and software developers who’d like to consume the BI Transactions API."},"overview":{"label":"Overview","description":"BI Transactions API offers an interface for customers and partners to retrieve consolidated booking transaction data from Egencia. The BI Transactions API is organised around REST /JSON over HTTPS for transaction data retrieval. This API accepts JSON requests and returns JSON responses, and uses standard HTTPs response codes, authentication, and verbs. "},"versioning":{"versions":[{"id":"1.0","change_description":"First stable version."}]},"error_codes":[{"code":"400","description":"Bad Request: Invalid input or request"},{"code":"401","description":"Unauthorized: authentication token empty, invalid or expired"},{"code":"403","description":"Forbidden: User not Validated for operation"},{"code":"404","description":"Not Found"},{"code":"422","description":"Invalid input: invalid or missing required input"},{"code":"500","description":"Internal Server Error: unable to process request."}],"api_details":{"label":"Reporting API details","description":"DOING a POST of BI API will return the metadata (hyperlinks) of the resource from where all the qualified transactions will be fetched in a paginated manner. You can page through the resource by making a GET request to the “next”URL provided in the paginated response. If there are no more pages, “next” will be set null. The users can page through any valid page number at any time using the Get request.","subheadings":[{"label":"API Developer Guidelines","description":"\t 1. Before implementing the reporting API, refer to the Developer Center to understand its contract.\n\t 2. Use POST and GET requests with the Developer Center Swagger endpoints to test credentials and ensure proper response receipt.\n\t 3. Authentication tokens, generated with client ID and secret, expire after one hour. \n\t\tRenew them by requesting a new token from the authentication endpoint if usage exceeds this duration.\n\t 4. When making repeated API calls, retrieve data for consecutive dates rather than fixed periods. \n\t\tFor daily updates, sequentially pull data for each day and only retrieve historical data as necessary.\n\t 5. Adhere to the API specifications as outlined in the Developer Center. \n\t\tTreat optional attributes as such; incorporate them only when available and ensure your code remains functional in their absence.\n\t 6. Handle any 4xx errors internally. Only reach out to Egencia support for 5xx error codes.\n\t 7. Refer to the \"Recent Updates\" section and click on \"Learn more\" for every month for latest updates.\n\t 8. For any technical support regarding the Reporting API with Egencia, please submit a community case with the following details: \n\t\tNames of the Reporting API endpoints (Air, Hotel, Fee, etc)\n\t\tImpacted API (if available)\n\t\tAPI Request body used for data retrieval\n\t\tDate/time of the API request execution.\n\t Notes:\n\t\tPoint_of_Sale_Type: Occasionally, the EGA data refresh process may be delayed. To identify EGA transactions, refer to \n\t\t\"Point_of_Sale_Type\"","subheadings":[{"label":"North America (NA) GDS Air Reconciliation ","description":"Egencia strives to provide better quality data and hence we are partnered with ARC/BSP to reconcile the NA air purchases with airlines. Please see section 'What is ARC and BSP?' for more details. This process of reconciliation is done in batches for a month’s air purchases. The section 'How to interpret the reconciled date and how to refresh these records?' explains how the API users could understand when the latest reconciled date of the data what they are trying to retrieve and how to refresh the data later if they are interested to fetch the reconciled records.","subheadings":[{"label":"What is ARC and BSP?","description":"ARC (Airlines Reporting Corporation) is an airline-owned company providing ticket distribution, reporting and settlement services for over 300 airline carriers and over 30,000 ARC-accredited Travel agency locations and Corporate Travel Departments in the United States, Puerto Rico and the U.S. Virgin Islands.\nBSP (Billing and Settlement Plan) is the equivalent to ARC and operates in 150 countries and territories.  It is a system designed to facilitate and simplify the selling, reporting and remitting procedures of IATA (International Air Transport Association)  Accredited Passenger Sales Agents, as well as improve financial control and cash flow for BSP Airlines. A truly worldwide system facilitating the settlement operations for airlines and agents, Over 80% of Worldwide airline revenues are ticketed via IATA travel agencies in the BSP system.\nThe ARC/BSP reconciliation process reconciles our purchase data against the airlines purchase data to ensure greater accuracy. \n\nFor more information on ARC reconciliation, please visit the ARC Website at https://www.arccorp.com.\nFor more information on BSP, visit  https://www.iata.org/en/services/finance/bsp/."},{"label":"How to interpret the reconciled date and how to refresh these records? ","description":"Reconciliation process is done only for NA GDS (Global distribution system) Air bookings. These booking records undergo reconciliation in batches throughout a month.  During reconciliation in a batch, the booking records could be updated or missing records could get inserted. If API is called before a batch is reconciled, there could be missing records or stale records.\nTo overcome this issue, we introduced the latest_reconciled_date concept. When a user try to hit the POST request, they will receive a latest reconciled date in the metadata along with the total records. This will help to identify if there are missing records in the date range provided in the request. If there is a latest reconciled date displayed then some records after the latest reconciled date displayed till the requested end date can be missing or can be stale.\nAlso, a new reconciled_records_only filter is provided for ALL LOB (Line Of Business) and Air LOB endpoints which can be set to true to fetch the NA GDS air records which undergo reconciliation. This will help customer or partner to refresh only the reconciled records. For example: \n\n If we requested for records between :: \n{\r\n  \"start_date\": \"2022-11-01 00:00:00\", \r\n  \"end_date\": \"2022-12-15 00:00:00\"\n}\r\n\n The response will contain a metadata latest_reconciled_date as shown below which is the latest reconciled date.  \n{\r\n  \"report_id\": \"e1252621-c7b6-403a-af36-46a6703d43a5\", \r\n  \"metadata\": \n{\r\n\t \"page_limit\": \"1000\",\n\t \"total_records\": \"257\" \n\t \"total_pages\": \"1\"\n \t\"latest_reconciled_date\": \"2022-11-27 00:00:00\"\n},\r\n\t \"_links\": {\r\n\t  \"last\": {\r\n\t\t\"href\": \"https://apis.egencia.com/bi/api/v1/transactions/e1252621-c7b6-403aaf3646a6703d43a5?page=1\"  \n\t\t}\r\n\t\t}\r\n}\r\nIn this response, we have a latest reconciled date which is older than the end date in the api request. In this case, customer or partner will need to call the API with reconciled_records_only for refreshing the booking records post latest reconciled date. \n\nN.B: A particular month’s reconciliation will be completed latest by 15th of the next month. So it is better to refresh the bookings on the 15th of the next month to ensure all bookings in a company is entirely retrieved for the month. This latest_reconciled_date element is not returned if there are no US or Canada Point of Sales data involved. Also, the date element will not be available, even for US/Canada Point of Sales, if the API is invoked before the batch is reconciled."}]}]}]},"enumerations":{"LOB type":[{"name":"Air","description":"Air - Line of business"},{"name":"CAR","description":"Car - Line of business"},{"name":"HOTEL","description":"Hotel - Line of business"},{"name":"TRAIN","description":"Train - Line of business"},{"name":"FEES","description":"Fees - Line of business"},{"name":"ALL","description":"All - Line of business"},{"name":"GROUND","description":"Ground - Line of business"}]},"http_verbs":[{"label":"Implementation Method","description":"Public BI Transactions API is a generic and secure solution to allow clients to access their previous booking  transaction data dynamically for different dates and other user query filters such as lob, locale, and currency-code  or report level.","values":[{"name":"Endpoint","description":"/v1/transactions"},{"name":"Method","description":"POST"},{"name":"Accept","description":"application/hal+json"},{"name":"Content-Type","description":"application/json"}]},{"label":"Offerings","values":[{"name":"All Line of business transactions (summary)","description":"Offers booking transaction data for all line of businesses which gives a consolidated summary view."},{"name":"Air transactions","description":"Offers booking transaction data for specifically Air transactions."},{"name":"Air transactions including segment information","description":"Offers booking transaction data for specifically Air including segment level information."},{"name":"Air transactions including ticketing information","description":"Offers booking transaction data for specifically Air including ticketing level information."},{"name":"Air transactions including leg information","description":"Offers booking transaction data for specifically Air transactions including leg level information."},{"name":"Hotel transactions","description":"Offers booking transaction data for specifically Hotel transactions."},{"name":"Train transactions","description":"Offers booking transaction data for specifically Train transactions."},{"name":"Train transactions including segment information","description":"Offers booking transaction data for specifically Train transactions including segment level information."},{"name":"Train transactions including ticketing information","description":"Offers booking transaction data for specifically Train transactions including ticket level information."},{"name":"Train transactions including leg information","description":"Offers booking transaction data for specifically Train transactions including leg level information."},{"name":"Car transactions","description":"Offers booking transaction data for specifically Car transactions."},{"name":"Fees Information","description":"Offers booking transaction data for specifically Fee transactions."}]}],"documentation_link":"https://apis.egencia.com/bi/docs/api-docs/transaction-data-service","api_updates":[{"date":"2026-07-15T00:00:00.000Z","updates":[{"label":"New attributes in \"Air Ticket\" API Response","description":"The Air API Response has been enhanced with a new attribute: \"prior_ticket_code\" at ticket level. For full specifications, please refer to the Request and Response Models section.","tags":[{"label":"New Attribute"},{"label":"Air"}]}]},{"date":"2026-06-18T00:00:00.000Z","updates":[{"label":"New attributes in \"Ground\" API Response","description":"The API response for Ground have been updated to include two new attributes: \"last_modified_date\" and \"record_id\". For full specifications, please refer to the Request and Response Models section.","tags":[{"label":"New Attribute"},{"label":"Ground"}]}]},{"date":"2026-06-15T00:00:00.000Z","updates":[{"label":"Reminder 3 - Advance Notice: Limiting Historical Data Access via Reporting API","description":"Starting July 1, 2026, the reporting API will limit historical data extraction to 12 months per request to maintain system performance and stability. Review your current API usage and prepare the necessary adjustments before the update. Note this was initially scheduled for March 31, 2026, but we're moving it to July 1, 2026 to ensure a smoother implementation. We will publish additional implementation details in the Developer Center soon.","tags":[{"label":"Breaking Change","styling_properties":{"text_color":"#0e1a23","background_color":"#ffc72c"}},{"label":"Update"}]}]},{"date":"2026-06-01T00:00:00.000Z","updates":[{"label":"New attributes in \"Air\", \"Hotel\", \"Train\" and \"Car\" API Responses","description":"The API responses for Air, Hotel, Train, and Car have been updated to include two new attributes: \"last_modified_date\" and \"record_id\". For full specifications, please refer to the Request and Response Models section.","tags":[{"label":"New Attribute"},{"label":"Air"},{"label":"Hotel"},{"label":"Train"},{"label":"Car"}]}]},{"date":"2026-05-15T00:00:00.000Z","updates":[{"label":"Reminder 2 - Advance Notice: Limiting Historical Data Access via Reporting API","description":"Starting July 1, 2026, the reporting API will limit historical data extraction to 12 months per request to maintain system performance and stability. Review your current API usage and prepare the necessary adjustments before the update. Note this was initially scheduled for March 31, 2026, but we're moving it to July 1, 2026 to ensure a smoother implementation. We will publish additional implementation details in the Developer Center soon.","tags":[{"label":"Breaking Change","styling_properties":{"text_color":"#0e1a23","background_color":"#ffc72c"}},{"label":"Update"}]}]},{"date":"2026-04-22T00:00:00.000Z","updates":[{"label":"New attributes in \"Car\" and \"Train\" API Response","description":"The Car API Response has been enhanced with following new attributes: \"trip_id\", \"trip_name\", \"carbon_emissions\" (in kg and lbs), and \"distance\" (in km and miles). Additionally, the Train API response now includes \"meeting_name\". For full specifications, please refer to the Request and Response Models section.","tags":[{"label":"New Attribute"},{"label":"Train"},{"label":"Car"}]}]},{"date":"2026-04-14T00:00:00.000Z","updates":[{"label":"Reminder 1 - Advance Notice: Limiting Historical Data Access via Reporting API","description":"Starting July 1, 2026, the reporting API will limit historical data extraction to 12 months per request to maintain system performance and stability. Review your current API usage and prepare the necessary adjustments before the update. Note this was initially scheduled for March 31, 2026, but we're moving it to July 1, 2026 to ensure a smoother implementation. We will publish additional implementation details in the Developer Center soon.","tags":[{"label":"Breaking Change","styling_properties":{"text_color":"#0e1a23","background_color":"#ffc72c"}},{"label":"Update"}]}]},{"date":"2026-03-02T00:00:00.000Z","updates":[{"label":"New attributes in \"Air\" API Response","description":"The Air API Response has been enriched with new attribute: \"flown_cabin_class\" at ticket, segment and leg levels. For full specifications, please refer to the Request and Response Models section.","tags":[{"label":"New Attribute"},{"label":"Air"}]}]},{"date":"2026-03-11T00:00:00.000Z","updates":[{"label":"New attributes in \"Train Ticket\" API Response","description":"The Train API Response has been enhanced with two new ticket-level attributes: \"trip_id\" and \"trip_name\". For full specifications, please refer to the Request and Response Models section.","tags":[{"label":"New Attribute"},{"label":"Train"}]}]},{"date":"2026-02-12T00:00:00.000Z","updates":[{"label":"New attributes in \"Train Ticket\" API Response","description":"The Train API Response has been enhanced with four new ticket-level attributes: \"tax_gst\", \"tax_hst\", \"tax_qst\" and \"tax_pst\". For full specifications, please refer to the Request and Response Models section.","tags":[{"label":"New Attribute"},{"label":"Train"}]}]},{"date":"2026-02-12T00:00:00.000Z","updates":[{"label":"Air Leg & Air Segment Reports: Time Zone Update","description":"We’ve updated the travel start date and travel end date fields in the Air Leg and Air Segment reports to display in the local time zone instead of UTC. This change aligns these reports with the Air Ticket report, which already uses local time, making it consistent across air reports. No underlying data is changing — only the time zone used for display. This update was released globally on February 12, 2026.","tags":[{"label":"Update"},{"label":"Air"}]}]},{"date":"2025-12-15T00:00:00.000Z","updates":[{"label":"Air Leg & Air Segment Reports: Time Zone Update","description":"We’re updating the travel start date and travel end date fields in the Air Leg and Air Segment reports to display in the local time zone instead of UTC. This change aligns these reports with the Air Ticket report, which already uses local time, making it consistent across air reports. No underlying data is changing — only the time zone used for display. This update will go live globally on February 5 and for Brazil on 5th January.","tags":[{"label":"Update"},{"label":"Air"}]}]},{"date":"2025-12-03T00:00:00.000Z","updates":[{"label":"New Attributes in All Transactions API response","description":"The All Transactions API Response has been enhanced with following new attributes: \"transaction_amount_local\", \"local_currency\", \"carbon_emissions\" (in kg and lbs), \"distance\" (in km and miles), \"is_approval_required\" and \"level_1_approver\". For full specifications, please refer to the Request and Response Models section.","tags":[{"label":"New Attribute"},{"label":"All Transactions"}]}]},{"date":"2025-11-25T00:00:00.000Z","updates":[{"label":"Advance Notice: Limiting Historical Data Access via Reporting API","description":"Starting July 1, 2026, the reporting API will limit historical data extraction to 12 months per request to maintain system performance and stability. Review your current API usage and prepare the necessary adjustments before the update. Note this was initially scheduled for March 31, 2026, but we're moving it to July 1, 2026 to ensure a smoother implementation. We will publish additional implementation details in the Developer Center soon.","tags":[{"label":"Breaking Change","styling_properties":{"text_color":"#0e1a23","background_color":"#ffc72c"}},{"label":"Update"}]}]},{"date":"2025-11-04T00:00:00.000Z","updates":[{"label":"Updates in \"Train\" and \"All Transactions\"","description":"We have deprecated an attribute from the Train endpoint under segment report level: \"ticket_number\" under “Train Segment details”. Please use ticket_code instead of ticket_number.We have also deprecated \"ticket_number\" under \"identifier\" section from All transaction endpoint. Added new field ticket_code under 'identifier' section and that can be used in place of ticket_number. We plan to remove these attribute after March 2026.","tags":[{"label":"Deprecation"},{"label":"Train"},{"label":"All transactions"}]},{"label":"Updates in \"Train\"","description":"We have deprecated an attribute from the Train endpoint: \"class_of_service_code\". We plan to remove this attribute after February 2026.","tags":[{"label":"Deprecation"},{"label":"Train"}]}]},{"date":"2025-10-24T00:00:00.000Z","updates":[{"label":"Advance Notice: Limiting Historical Data Access via Reporting API","description":"Starting March 31, 2026, we will limit data extraction in the reporting API to 12 months per request. We are making this change to maintain system performance and stability. Review your current API usage and prepare the necessary adjustments before the update. We will publish additional implementation details in the Developer Center soon.","tags":[{"label":"Breaking Change","styling_properties":{"text_color":"#0e1a23","background_color":"#ffc72c"}},{"label":"Update"}]}]},{"date":"2025-08-29T00:00:00.000Z","updates":[{"label":"Updates in \"Train\"","description":"We have deprecated an attribute from the Train endpoint: \"class_of_service_code\". We plan to remove this attribute after February 2026.","tags":[{"label":"Deprecation"},{"label":"Train"}]}]},{"date":"2025-08-29T00:00:00.000Z","updates":[{"label":"New attributes in \"Hotel\"","description":"The Hotel API Response has been enhanced with two new attributes: \"trip_id\" and \"trip_name\". This trips data is available globally and backfilled to July 2024. For full specifications, please refer to the Request and Response Models section.","tags":[{"label":"New Attribute"},{"label":"Hotel"}]}]},{"date":"2025-08-07T00:00:00.000Z","updates":[{"label":"Data update in Air report","description":"We have completed a set of updates to standardize data formatting in the Air Report. All amount fields now default to \"0\" instead of blank. All country, airline, and airport names are provided in English only, replacing previously localized versions. Location1 and Location2 attributes have also been updated to use the Airport Display International Name format, which includes country names for better clarity and consistency across all points of sale.","tags":[{"label":"Update"},{"label":"Air"}]}]},{"date":"2025-08-04T00:00:00.000Z","updates":[{"label":"New Attributes in \"Air\" and \"Train\"","description":"The Air API Response has been enhanced with two new ticket-level attributes: \"trip_id\" and \"trip_name\". It is available only for EMEA/APAC and has been extended back to August 2024. Additionally, the Train API Response now includes a new segment-level attribute: \"operating_carrier_segment\". For full specifications, please refer to the Request and Response Models section.","tags":[{"label":"New Attribute"},{"label":"Air"},{"label":"Train"}]}]},{"date":"2025-08-04T00:00:00.000Z","updates":[{"label":"Advance Notice: Limiting Historical Data Access via Reporting API","description":"Starting March 31, 2026, we will limit data extraction in the reporting API to 12 months per request. We are making this change to maintain system performance and stability. Review your current API usage and prepare the necessary adjustments before the update. We will publish additional implementation details in the Developer Center soon.","tags":[{"label":"Breaking Change","styling_properties":{"text_color":"#0e1a23","background_color":"#ffc72c"}},{"label":"Update"}]}]},{"date":"2025-07-15T00:00:00.000Z","updates":[{"label":"New Attributes in \"Car\" and \"Train\"","description":"A new \"violated_policy_1\" attribute is now available for both Car and Train reports under the “Policy” section. It captures the name of the policy violated in the out-of-policy transaction. For details, see the \"Request and Response Models\" section.","tags":[{"label":"New Attribute"},{"label":"Car"},{"label":"Train"}]}]},{"date":"2025-04-23T00:00:00.000Z","updates":[{"label":"New Attributes in \"Air\"","description":"We have added three new attributes to the Air API Response at Ticket level: \"is_fly_america_compliant\", \"refundability_type\" and \"changeability_type\" under the \"Air Transaction Response\" section. For more details, please consult the \"Request and Response Models\" section.","tags":[{"label":"New Attribute"},{"label":"Air"}]}]},{"date":"2025-03-13T00:00:00.000Z","updates":[{"label":"New Attributes in \"Air\" and \"Hotel\"","description":"We have added two new attributes to the Air API Response: \"violated_policy_1\" and \"violated_policy_2\" under the \"Policy details\" section, and one attribute to the Hotel Response \"meeting_name\". For more details, please consult the \"Request and Response Models\" section.","tags":[{"label":"New Attribute"},{"label":"Air"},{"label":"Hotel"}]}]},{"date":"2025-03-03T00:00:00.000Z","updates":[{"label":"New Attribute - \"miscellaneous_transport_type\"","description":"We have added a new attribute to the \"All transactions\" API Response: \"miscellaneous_transport_type\". For more details, please consult the \"Request and Response Models\" section.","tags":[{"label":"New Attribute"}]}]},{"date":"2025-01-30T00:00:00.000Z","updates":[{"label":"Updates in the \"Hotel\"","description":"We have deprecated two attributes from the Hotel endpoint: \"feetype\" and \"change_fees\". We plan to remove these attributes after Oct 2025."}]},{"date":"2024-11-25T00:00:00.000Z","updates":[{"label":"Updates in the \"Air\"","description":"Deprecated attributes from the Air endpoint have been successfully removed to maintain API consistency."}]},{"date":"2024-11-21T00:00:00.000Z","updates":[{"label":"Updates in the \"Car\" & \"Ground\"","description":"Starting 7th Dec, we will remove transactions marked as “Is Special Request” = “Yes” from the Car and Ground endpoints. They will be available in the \"transactions\" endpoint."}]},{"date":"2024-10-17T00:00:00.000Z","updates":[{"label":"Updates in the \"Air\"","description":"Removal of deprecated attributes for Air endpoint will be conducted on or after 15th Nov."}]},{"date":"2024-10-16T00:00:00.000Z","updates":[{"label":"Updates in the \"Hotel\"","description":"Deprecated attributes from the Hotel endpoint have been successfully removed to maintain API consistency."}]},{"date":"2024-10-15T00:00:00.000Z","updates":[{"label":"Point_of_Sale_Type","description":"Occasionally, the EGA data refresh process may be delayed. To identify EGA transactions, refer to \"Point_of_Sale_Type\"."}]},{"date":"2024-09-19T00:00:00.000Z","updates":[{"label":"Updates in the \"Train\"","description":"Deprecated attributes from the Train endpoint have been successfully removed to maintain API consistency."}]},{"date":"2024-09-18T00:00:00.000Z","updates":[{"label":"Updates in the \"Fee\"","description":"We added a new \"Point_of_Sale_Type\" attribute to the API Responses for \"All Transactions\", \"Air\", and \"Hotel\". We also included two new attributes, \"Trip_ID\" and \"Trip_Name\", to the Fee API Response. For further details, please refer to the \"Request and Response Models\" section."}]},{"date":"2024-09-05T00:00:00.000Z","updates":[{"label":"Updates in the \"Car\"","description":"Deprecated attributes from the Car endpoint have been successfully removed to maintain API consistency."}]},{"date":"2024-08-26T00:00:00.000Z","updates":[{"label":"Updates in the \"Fee\"","description":"Deprecated attributes from the Fees endpoint have been successfully removed to maintain API consistency."}]},{"date":"2024-08-06T00:00:00.000Z","updates":[{"label":"Updates in the \"Fee\"","description":"We have added four new attributes to the Fee API Response: \"is_waived\", \"waived_amount\", \"confirmation_number\", and \"line_of_business\". The attribute \"confirmation_number\" is added under the \"identifier\" section. For more details, please consult the \"Request and Response Models\" section."}]},{"date":"2024-07-26T00:00:00.000Z","updates":[{"label":"Final reminder about removal of deprecated attributes in Reporting API","description":"This is a final reminder about the upcoming removal of reporting API data fields/attributes. These outdated/deprecated attributes will be removed in multiple phases over the next three months: Ground in the first week of August, Fees in the third week of August, Car in the first week of September, Train in the third week of September, Hotel in the first week of October, and Air in the third week of October."}]},{"date":"2024-06-26T00:00:00.000Z","updates":[{"label":"Updates in \"Dynamic Rate Cap Savings\"","description":"We have added six new attributes to the Hotel API Response. Five of these attributes are part of a new \"Dynamic Rate Cap\" section, while the Dynamic_Rate_Cap_Savings attribute is listed under Savings. To understand these attributes and their usage, please consult the \"Request and Response Models\" section in the Developer Center."}]},{"date":"2024-06-10T00:00:00.000Z","updates":[{"label":"Update on deprecated attributes removal","description":"The timeline to remove the outdated \"deprecated\" data fields is moved from 1st June to 1st August, giving you two more months to complete any necessary work to incorporate the removed data fields. We have updated descriptions for these 7 deprecated attributes; please refer to them. Read this list as \"section/attribute name\" : \"Air transaction response/airline_name\", \"Duration of booking/end\", \"Duration of booking/start\", \"Hotel transaction response/hotel_savings\", \"Price information/change_fee_amount\", \"Train origin destination details/destination_country_bidirectional\", \"Train transaction response/city_name_pair_unidirectional\"."}]},{"date":"2024-02-16T00:00:00.000Z","updates":[{"label":"Alert: Notification about deprecated attributes removal","description":"Starting June 1st, 2024, we will remove over 100 deprecated data attributes to improve the reporting API’s performance. You can find the full list of data fields that we plan to remove in this link: \"https://www.egencia.com/developer-center/api-details/reporting-api\". These fields are marked as \"Deprecated\" in the description column. This change may require you to make changes in how you interact with our Reporting API, as this change will update the list of available data fields for the future. If you have any concerns or require assistance, please do not hesitate to contact our support team."}]},{"date":"2024-01-25T00:00:00.000Z","updates":[{"label":"Updates in \"Air Segment API\"","description":"We Have added the \"haul\" attribute to our Air segment API. This classifies flights as short (≤784.87 Km), medium (>784.87 to ≤3700 Km), or long haul (>3700 Km). Combined with cabin class data, it empowers customers to independently determine CO2 emissions for each flight segment using their chosen CO2 coefficient."}]},{"date":"2023-12-21T00:00:00.000Z","updates":[{"label":"Updates in \"NDC\"","description":"We have introduced the \"is_ndc\" attribute in the Air API Response. This new \"Boolean value\" attribute indicates whether bookings are made via the New Distribution Capability (NDC) channel. With this attribute, you can distinguish air bookings made with NDC fares to monitor spending, manage unused tickets, drive supplier negotiations, etc.\nIt has data available back until 2019."}]}]}