WSF Terminals API

API Access Code

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.

Register »

GET /cacheflushdate


Valid Accept Headers

application/json text/xml


Description

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:

/terminalbasics
/terminalbasics/{TerminalID}
/terminalbulletins
/terminalbulletins/{TerminalID}
/terminallocations
/terminallocations/{TerminalID}
/terminaltransports
/terminaltransports/{TerminalID}
/terminalverbose
/terminalverbose/{TerminalID}
/terminalwaittimes
/terminalwaittimes/{TerminalID}

GET /terminalbasics?apiaccesscode={APIAccessCode}

GET /terminalbasics/{TerminalID}?apiaccesscode={APIAccessCode}


Valid Accept Headers

application/json text/xml


Description

This operation retrieves the most basic / brief information pertaining to terminals. A TerminalID, or unique terminal identifier, may be optionally passed to retrieve a specific terminal. 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.

GET /terminalbulletins?apiaccesscode={APIAccessCode}

GET /terminalbulletins/{TerminalID}?apiaccesscode={APIAccessCode}


Valid Accept Headers

application/json text/xml


Description

This operation retrieves alerts and bulletins associated with terminals. Each terminal may have zero or more bulletins assigned to it. A TerminalID, or unique terminal identifier, may be optionally passed to retrieve a specific terminal. 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.

GET /terminallocations?apiaccesscode={APIAccessCode}

GET /terminallocations/{TerminalID}?apiaccesscode={APIAccessCode}


Valid Accept Headers

application/json text/xml


Description

This operation retrieves detailed location information pertaining to terminals. A TerminalID, or unique terminal identifier, may be optionally passed to retrieve a specific terminal. 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.

GET /terminalsailingspace?apiaccesscode={APIAccessCode}

GET /terminalsailingspace/{TerminalID}?apiaccesscode={APIAccessCode}


Valid Accept Headers

application/json text/xml


Description

This operation reflects terminal condition data (the number of drive-up and reservation spaces available for select departures). A TerminalID, or unique terminal identifier, may be optionally passed to retrieve a specific terminal. A valid API Access Code from the WSDOT Traveler API must be passed as part of the URL string.

This data changes very frequently (potentially every 5 seconds). Please do not cache results in your application for an extended period of time.

GET /terminaltransports?apiaccesscode={APIAccessCode}

GET /terminaltransports/{TerminalID}?apiaccesscode={APIAccessCode}


Valid Accept Headers

application/json text/xml


Description

This operation provides helpful information for terminal commuters (including parking notes, vehicle-specific tips, etc). A TerminalID, or unique terminal identifier, may be optionally passed to retrieve a specific terminal. 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.

GET /terminalverbose?apiaccesscode={APIAccessCode}

GET /terminalverbose/{TerminalID}?apiaccesscode={APIAccessCode}


Valid Accept Headers

application/json text/xml


Description

This operation retrieves highly detailed information pertaining to terminals. It should be used if you need to reduce the "chattiness" of your application and don't mind receiving a larger payload of data. The results include and expand on what's already available through the following operations:

/terminalbasics
/terminalbasics/{TerminalID}
/terminalbulletins
/terminalbulletins/{TerminalID}
/terminallocations
/terminallocations/{TerminalID}
/terminaltransports
/terminaltransports/{TerminalID}
/terminalwaittimes
/terminalwaittimes/{TerminalID}

TerminalID, or unique terminal identifier, may be optionally passed to retrieve a specific terminal. 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.

GET /terminalwaittimes?apiaccesscode={APIAccessCode}

GET /terminalwaittimes/{TerminalID}?apiaccesscode={APIAccessCode}


Valid Accept Headers

application/json text/xml


Description

This operation retrieves tips and wait time conditions for both vehicles and walk-on passengers. A TerminalID, or unique terminal identifier, may be optionally passed to retrieve a specific terminal. 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.