Most of the REST operations require that an API Access Code be passed as part of the URL string. In order to get a valid API Access Code, please register your email address with the WSDOT Traveler API.
application/json text/xml
Some of the retrieval operations in this service return data that changes infrequently. As a result, you may wish to cache it in your application. Use the /cacheflushdate operation to poll for changes. When the date returned from this operation is modified, drop your application cache and retrieve fresh data from the service.
The following operations return data that changes infrequently and can be cached in the manner described above:
/validdaterange
/terminals
/terminalmates
/terminalcombo
/terminalcomboverbose
/farelineitemsbasic
/farelineitems
/farelineitemsverbose
/faretotals
application/json text/xml
This operation retrieves a date range for which fares data is currently published & available. A valid API Access Code from the WSDOT Traveler API must be passed as part of the URL string.
Please consider using /cacheflushdate to coordinate the caching of this data in your application.
application/json text/xml
This operation retrieves valid departing terminals for a given trip date. A valid trip date may be determined using /validdaterange. Please format the trip date input as 'YYYY-MM-DD' (eg. '2014-04-01' for a trip date occurring on April 1, 2014). A valid API Access Code from the WSDOT Traveler API must also be passed as part of the URL string.
Please consider using /cacheflushdate to coordinate the caching of this data in your application.
application/json text/xml
This operation provides arriving terminals for a given departing terminal and trip date. A valid departing terminal may be found by using /terminals. Similarly, a valid trip date may be determined using /validdaterange. Please format the trip date input as 'YYYY-MM-DD' (eg. '2014-04-01' for a trip date occurring on April 1, 2014). A valid API Access Code from the WSDOT Traveler API must also be passed as part of the URL string.
Please consider using /cacheflushdate to coordinate the caching of this data in your application.
application/json text/xml
This operation describes what fares are collected for a given departing terminal, arriving terminal and trip date. A valid departing terminal may be found by using /terminals while a valid arriving terminal may be found by using /terminalmates. Similarly, a valid trip date may be determined using /validdaterange. Please format the trip date input as 'YYYY-MM-DD' (eg. '2014-04-01' for a trip date occurring on April 1, 2014). A valid API Access Code from the WSDOT Traveler API must also be passed as part of the URL string.
Please consider using /cacheflushdate to coordinate the caching of this data in your application.
application/json text/xml
This operation retrieves fare collection descriptions for all terminal combinations available on a given trip date. A valid trip date may be determined using /validdaterange. Please format the trip date input as 'YYYY-MM-DD' (eg. '2014-04-01' for a trip date occurring on April 1, 2014). A valid API Access Code from the WSDOT Traveler API must also be passed as part of the URL string.
Please consider using /cacheflushdate to coordinate the caching of this data in your application.
application/json text/xml
This operation retrieves the most popular fares for either round trip or one-way departures available for a given departing terminal, arriving terminal and trip date. For round trip input please use 'true' to indicate round trip or 'false' to indicate a one-way journey. A valid departing terminal may be found by using /terminals while a valid arriving terminal may be found by using /terminalmates. Similarly, a valid trip date may be determined using /validdaterange. Please format the trip date input as 'YYYY-MM-DD' (eg. '2014-04-01' for a trip date occurring on April 1, 2014). A valid API Access Code from the WSDOT Traveler API must also be passed as part of the URL string.
Please consider using /cacheflushdate to coordinate the caching of this data in your application.
application/json text/xml
This operation retrieves fares for either round trip or one-way departures available for a given departing terminal, arriving terminal and trip date. For round trip input please use 'true' to indicate round trip or 'false' to indicate a one-way journey. A valid departing terminal may be found by using /terminals while a valid arriving terminal may be found by using /terminalmates. Similarly, a valid trip date may be determined using /validdaterange. Please format the trip date input as 'YYYY-MM-DD' (eg. '2014-04-01' for a trip date occurring on April 1, 2014). A valid API Access Code from the WSDOT Traveler API must also be passed as part of the URL string.
Please consider using /cacheflushdate to coordinate the caching of this data in your application.
application/json text/xml
This operation retrieves round trip and one-way fares for all valid departing and arriving terminal combinations on a given trip date. A valid trip date may be determined using /validdaterange. Please format the trip date input as 'YYYY-MM-DD' (eg. '2014-04-01' for a trip date occurring on April 1, 2014). A valid API Access Code from the WSDOT Traveler API must also be passed as part of the URL string.
Please consider using /cacheflushdate to coordinate the caching of this data in your application.
application/json text/xml
This operation totals a set of fares & associated quantities for either a round trip or one-way journey, given a departing terminal, arriving terminal and trip date. Fare line item ID is a comma delimited array of line items you'd like to have totalled. Use /farelineitems to find valid fare line item ID values. Quantity is also a comma delimited array. Quantity values must be greater than or equal to zero. The same index in the fare line item ID and quantity input arrays must associate a fare with a quantity. For round trip input please use 'true' to indicate round trip or 'false' to indicate a one-way journey. A valid departing terminal may be found by using /terminals while a valid arriving terminal may be found by using /terminalmates. Similarly, a valid trip date may be determined using /validdaterange. Please format the trip date input as 'YYYY-MM-DD' (eg. '2014-04-01' for a trip date occurring on April 1, 2014). A valid API Access Code from the WSDOT Traveler API must also be passed as part of the URL string.
Please consider using /cacheflushdate to coordinate the caching of this data in your application.