- Airport Data
- Airport data coverage has been expanded to more than 20000 commercial and general aviation airports worldwide.
- The airports response object now includes discrete fields for ICAO code, IATA code, and FAA identifier.
- API users can expect air segment objects to hold the most appropriate airport code in the Origin and Destination fields based on the source data.
- Example: An air segment that is based on the source data DFW/OGG will have DFW/OGG and not KDFW/PHOG.
- The "id" attribute is the unique and canonical identifier for the airport. This is typically the ICAO code when one has been assigned or the more appropriate of the IATA or FAA codes.
- The "code" attribute is deprecated. Use "id" or one of the discrete airport code fields.
- New The Webhooks documentation has been updated to include the new trip_segment webhooks events.
- trip_segment events allow consumers to maintain a copy of trips and the segments contained within each trip in their own datastore.
- trip_segment.added events indicate that an existing segment was added to the trip from another trip. This happens as trips are adjusted when new data arrives for processing.
- trip_segment.removed events indicate that an existing segment was removed from the trip and added to another trip. This happens as trips are adjusted when new data arrives for processing.
- Consumers that previously used the "parents" and "children" modifiers should switch to using these new events.
- New Segment endpoints now allow the "source" object to be included in the response. See the request parameters for each segment endpoint. Example: Air Segment.
- 64-bit integer string IDs have been enabled for many Traxo data objects.
- See the Data Types and Values section of the overview for more info.
- The Traxo API definitions were updated on April 25, 2017 to show where IDs of this type were being used or where they are expected to be used.
- As of October 1, 2017, connections to Traxo services (including Traxo APIs) must use TLS 1.1 or TLS 1.2. Connections using TLS 1.0 will no longer be accepted.
- New App Tokens / client_credentials grant
- The Traxo authorization server now supports the "client_credentials" OAuth 2 grant type.
- This grant type can be used to generate an application-level access token that can be used to make requests to any endpoint that requires client credentials.
- API endpoints that have previously required the client_id and client_secret headers will now accept and prefer an app token.
- A member access token may also be used to access endpoints that are not member-specific. A separate app token is not necessary. This simplifies connection and request management when working with a member token that also needs generic resources (locations, sources, etc).
- Email Parsing - Added "credit" receipt item type to folio parsing.
- Updated the Overview Data Types and Values documentation to include a section on "Identifiers".
- This section is intended to make developers aware that Traxo does and
may use 64-bit integer IDs delivered as string values and should design their
applications and storage appropriately.
- The Traxo API definitions were updated on April 25, 2017 to show where IDs of this
type were being used or where they are expected to be used.
- Many Traxo resources will to transition to this form of ID during August 2017.
- Activity segment type "Ferry" has been removed due to lack of usage and replaced
with a more generic type "Transportation". This type will be used for taxis, limos,
shared car services like Uber and Lyft. It is also suitable for water
- Email Parsing - Bug fix - Ensure the price_details "value" attribute is always
returned as a numeric string. Previously, there was an inconsistency in the response
type between string and float. The numeric string is preferred because some
currencies and locales use separators like commas that are incompatible with the
float type. Example: "1200,25".
- OpenAPI ("Swagger") Specifications / API Explorers
- OpenAPI specs updated with more field-level example data.
- OpenAPI specs updated to show 64-bit integer string IDs where
they are currently used or may be added in the future. Traxo IDs are always
delivered as strings to avoid long integer issues when used with languages
- The OpenAPI specs are used to drive the Traxo API Explorers for the
main API and the
email parsing API.