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
/terminalsandmates
/terminalsandmatesbyroute
/terminalmates
/routes
/routeshavingservicedisruptions
/routedetails
/activeseasons
/schedroutes
/sailings
/allsailings
/timeadj
/timeadjbyroute
/timeadjbyschedroute
/schedule
/scheduletoday
/alerts
application/json text/xml
This operation retrieves a date range for which schedule 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 retrieves all valid departing and arriving terminal combinations 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 valid departing and arriving terminal combinations for a given trip date and route. Valid routes may be found by using /routes. 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 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 retrieves the most basic / brief information pertaining to routes. If only a trip date is included in the URL string, all routes available for that date of travel are returned. If a trip date, departing terminal and arriving terminal are included then routes in the resultset are filtered to match accordingly. Valid departing and arriving terminals may be found using /terminalsandmates. 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 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 basic / brief information for routes currently associated with service disruptions. 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 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 highly detailed information pertaining to routes. If only a trip date is included in the URL string, all routes available for that date of travel are returned. If a trip date, departing terminal and arriving terminal are included then routes in the resultset are filtered to match accordingly. Along the same lines, including only a trip date and route will filter the resultset to a single route. Valid departing and arriving terminals may be found using /terminalsandmates while valid routes may be found using /routes. 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 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 a summary of active seasons. 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 provides a listing of routes that are active for a season. For example, "Anacortes / Sidney B.C." may be a valid route, but if it's not scheduled to run during Winter 2014, it won't be returned as part of the Winter 2014 scheduled routes resultset. Results will include all known scheduled routes spanning current and upcoming seasons or, alternatively, results can be filtered to only include scheduled routes for a specific season (when the season is specified with a ScheduleID value). Seasons may be determined using /activeseasons. 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 provides sailings for a particular scheduled route. Sailings are departure times organized by direction of travel (eastbound / westbound), days of operation groups (daily, weekday, weekend, etc) and, in some cases, date ranges (eg. Early Fall / Late Fall). Sailings largely mimic the groupings of departures found on the printed PDF version of the schedule. Scheduled routes may be determined using /schedroutes. 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 provides all sailings for a particular scheduled route. Sailings are departure times organized by direction of travel (eastbound / westbound), days of operation groups (daily, weekday, weekend, etc) and, in some cases, date ranges (eg. Early Fall / Late Fall). Sailings largely mimic the groupings of departures found on the printed PDF version of the schedule. Scheduled routes may be determined using /schedroutes. 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 provides a listing of all additions and cancellations that deviate on specific dates from the scheduled times found in the /sailings resultset (eg. tidal cancellations affecting Port Townsend departures on 9/9/2014). 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 provides a listing of all additions and cancellations for a route that deviate on specific dates from the scheduled times found in the /sailings resultset (eg. tidal cancellations affecting Port Townsend departures on 9/9/2014). A valid route may be determined using /routes. 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 provides a listing of all additions and cancellations for a scheduled route that deviate on specific dates from the scheduled times found in the /sailings resultset (eg. tidal cancellations affecting Port Townsend departures on 9/9/2014). A valid scheduled route may be determined using /schedroutes. 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 provides departure times for either a trip date and route or a trip date and terminal combination. The resultset accounts for all contingencies, sailing date ranges and time adjustments. Valid departing and arriving terminals may be found using /terminalsandmates while valid routes may be found using /routes. 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 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 today's departure times for either a terminal combination or a route. Valid departing and arriving terminals may be found using /terminalsandmates while valid routes may be found using /routes. For the OnlyRemainingTimes value, please indicate 'true' if departure times prior to now should not be included in the resultset and 'false' if they should be included in the resultset. 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 provides alert information tailored for routes, bulletins, service disruptions, etc. 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.