Change Log


  • Added the "resource_id" parameter to the event and webhook response objects. This is the identifier of the resource represented by the event.


  • Added the "org_id" parameter to the segment response objects.
  • Added the "source_id" and "source_type" parameters to the segment response objects.

Historical Changes



  • Added the "org_id" parameter to the member response object.
  • All Traxo members belong to a specific "Organization". Over time, the "org_id" parameter will be added to objects throughout the system. API consumers should store this value along with the "id" of each member and other identifying attributes as needed.


  • New developer management experience
    • We are happy to announce a new developer management experience that will provide easy access to our new platform features, improved usability, and built-in support functionality.
    • This new application is replacing the logged-in experience of the Traxo developer portal. Documentation and reference materials will continue to be available at
    • Please contact support if you need help getting started with the new console application.


  • Email Parsing
    • The email parsing results object now includes a top-level "info" object. This object contains general information about the email and the email contents. To provide flexibility, the keys and values of this object are optional.
    • Updated email parsing documentation to add the "info" object to the response format examples.
    • Added new response format examples to show typical error messages


  • As of February 8, 2019, all connections to Traxo services must use TLS 1.2 or greater. Connections using TLS 1.1 and below will no longer be accepted.


  • Reminder: As of February 1, 2019, connections to Traxo services (including Traxo APIs) must use TLS 1.2 or greater. Connections using TLS 1.1 and below will no longer be accepted.
  • Webhooks behavior change expected during 1H 2019
    • If you use multiple API clients within a single developer account to segment environments (prod, test, etc) and expect registered webhook URLs to receive events only on behalf of the API client that owns it, please contact Customer Support as soon as possible.
    • Upcoming changes to the ownership of API clients and webhooks within your developer account will cause all events for the developer account to be delivered to all registered webhooks.



  • Reminder: As of February 1, 2019, connections to Traxo services (including Traxo APIs) must use TLS 1.2 or greater. Connections using TLS 1.1 and below will no longer be accepted.


  • Action Required: As of February 1, 2019, connections to Traxo services (including Traxo APIs) must use TLS 1.2 or greater. Connections using TLS 1.1 will no longer be accepted. See PCI Security Standards Council mandate for additional information.


  • 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 transportation.


  • 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 like javascript that can interpret these as float values unexpectedly.
    • The OpenAPI specs are used to drive the Traxo API Explorers for the main API and the email parsing API.




  • Added details regarding JSON to the Overview along with a statement that API responses may contain null or empty string values indicating an absence of data. API consumers should handle those values appropriately.


  • Added "images" object to selected response objects.
  • This method of specification allows the developer to fetch only the image that they need when multiple sizes or formats are available.
  • To build an image url, concatenate prefix + modifier + suffix.
  • trip image modifiers: 64x64, 128x128, 256x256, 512x512


  • New Email Parsing. Added documentation regarding the Traxo email parsing solutions now available in preview release.


  • Updated the Connecting documentation to clarify the need to use HTTP POST when exchanging either an authorization code or a refresh token for an access token.


  • Updated the Webhooks documentation regarding custom payloads.
  • Added data selector: id. This can be used to receive only the ID of the object associated with the event.
  • Added data selector: children. For trip events, contains an array of child segments.
  • Added notes that the selectors are optional and independent.
  • Added recommendations on selector usage.
  • Added examples showing parents (for segment events) and children (for trip events).



  • Added the Webhooks documentation link to the top-nav.


  • Added "harvested" parameter to itinerary, trip, and segment response objects.
  • This parameter may be used to detect whether we obtained the object data from a supplier and adjust your user interface accordingly.


  • Added new location endpoints to lookup airports, rail stations, country and admin codes
  • Added new Activity segment "activity_type" to support specific types of activities (Meeting, Theater, Restaurant, etc...)
  • Added support for Activity segment end location (end_address1, end_address2, end_city).
  • If you were previously using the "time_zone_id" response parameter, please switch to the start_/end_ time_zone_id parameters.



  • The API Explorer has been updated to match the latest set of supported input fields. Specifically, price and currency fields have been added to all segment types.
  • The Traxo MemberID parameter (member_id) has been added to Account, Trip, Itinerary, and each Segment response object to support API clients that need a member reference when handling Webhooks events.


  • Documentation updates. These updates are on-going. The API Explorer will always have a most complete and detailed information on each of the API methods.


  • API Version 2 is now live. API Version 1 will be available until June 1, 2013.


  • The developer portal has a new url! Please update your links to


  • API V2 Pre-release
    • More RESTlike, more semantic
    • Expanded features
  • New developer portal launched!
    • Clean, responsive design - access it from your mobile device
    • Interactive API explorer (live documentation)


  • Internal changes. No customer-facing impact expected. Please report any issues.
  • "itinerary_id" parameter officially added to Trip objects. Integer. Itinerary endpoints will be provided in a future release.
  • "type" parameter added to Segment objects. String.
    • Possible values: Air, Car, Hotel, Activity, Cruise, Rail


  • Internal changes. No customer-facing impact expected. Please report any issues.


  • Added common time zone abbreviations (i.e. "CDT", "PST", "EDT") to the Objects listed below:
    • Trip
    • AirSegment
    • CarSegment
    • HotelSegment
    • RailSegment
    • ActivitySegment
  • This new field is usually named "time_zone" and may appear with relevant prefixes for transportation segments that have differing start or end points or dates/times.
  • This new field should be used for display near the associated local date/time. It may contain up to 4 characters.
  • Use only the appropriate "time_zone_id" and associated date/time parameter to perform any date/time calculations.


  • The image assets returned within the segment objects have been upgraded. We think you will like these new assets, but if you would like to continue using the old assets, please grab a copy here before June 1, 2013:
    • Air:
    • Car:
    • Hotel:
    • Activity:
    • Rail:


Added image_url parameter to the segment object response. This url will point to a image representative of the segment and will typically be a larger image than is provided via the icon_url parameter.


Traxo members may manually disconnect from API clients via their profile settings page.
OAuth flow usability improvements for IE browsers (IE8, specifically)
Fields added to the travel accounts response /accounts
Rail segments added to /trip, /trip/past, /trip/upcoming, /trip/current, /trip/segments, /trip/search
Fixed a very rare issue where certain trip segments were omitted from the responses.
Ensure that our default icon url is returned for activity segments that do not have a custom icon image.
New endpoint: /trip/search
Added expected error responses to the "read" endpoints.


Improved handling of international characters in responses
Added status parameter to trip and segment responses. Values: Active, Past Date, Deleted
Included deleted segments in the /trip/search response


Improved handling of international characters in responses
Implemented enhanced error responses for "read" endpoints.
Added Error Responses section to the Overview.
Updating method documentation with possible error codes (in-progress)


Updated curl examples for each method to include the version ("v1") identifier.


Extended Refresh Token expiration to 1 year.
Began phasing in uri-based API versioning. See the Versioning section.


Added Olson time_zone_id parameters where applicable (trip, segments, etc).
Added created/updated timestamps where applicable.
Enhanced trip "meta" data: verified (Y/N), distance (miles), duration (decimal days).
Improved error handling and display on OAuth pages.
Connecting page:
    Added notice of enforcement on redirect_uri and state parameters based on industry best practices.
    Added section: Refreshing an access token.
Established token/code lifetimes:
    auth code: 1 minute
    access_token: 24 hours
    refresh_token: 30 days
Updated/synchronized documented parameters with responses.


OAuth 2.0 Endpoints activated. See Connecting.
Developer portal converted to OAuth mode (existing users may receive an email from the system).
Existing applications have been converted to use OAuth.
    You will need to login to the portal and provide a redirect_url and updated app properties.
    Existing api_keys have been grandfathered and will remain usable until 3/31/2013.
Documentation updated to use "access_token" in place of "t".
Known Limitations/Issues - OAuth
    Creating a new Traxo member account from /oauth/authenticate is not yet implemented.


Initial OAuth 2.0 documentation available. See Connecting.



Added "url" parameter to Member and Trip objects to allow linking to the objects on
Added "icon_url" parameters to Air, Car, Hotel, and Activity segment objects.
Created new Objects documentation section to show the typical content for each response object.
Updated methods examples to link to the new Objects page.