Most of the SOAP operations require that an API Access Code be passed either directly to the web method or, for some older service proxies, delivered as part of a SOAP header. The API Access Code is delivered using the APIAccessCode property on the APIAccessHeader object. In order to get a valid API Access Code, please register your email address with the WSDOT Traveler API.
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 GetCacheFlushDate() 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:
GetAllTerminalBasicDetails()
GetSpecificTerminalBasicDetail(TerminalMsg)
GetAllTerminalBulletins()
GetSpecificTerminalBulletin(TerminalMsg)
GetAllTerminalLocations()
GetSpecificTerminalLocation(TerminalMsg)
GetAllTerminalTransportationOptions()
GetSpecificTerminalTransportationOption(TerminalMsg)
GetAllTerminalVerboseDetails()
GetSpecificTerminalVerboseDetail(TerminalMsg)
GetAllTerminalWaitTimes()
GetSpecificTerminalWaitTime(TerminalMsg)
These operations retrieve the most basic / brief information pertaining to terminals. GetAllTerminalBasicDetails retrieves data for all terminals. Meanwhile, GetSpecificTerminalBasicDetail is passed a TerminalID, or unique terminal identifier, as part of the TerminalMsg parameter for cases when only a specific terminal is required. A valid API Access Code from the WSDOT Traveler API must be provided.
Please consider using GetCacheFlushDate() to coordinate the caching of this data in your application.
These operations retrieve alerts and bulletins associated with terminals. Each terminal may have zero or more bulletins assigned to it. GetAllTerminalBulletins retrieves data for all terminals. Meanwhile, GetSpecificTerminalBulletin is passed a TerminalID, or unique terminal identifier, as part of the TerminalMsg parameter for cases when only a specific terminal is required. A valid API Access Code from the WSDOT Traveler API must be provided.
Please consider using GetCacheFlushDate() to coordinate the caching of this data in your application.
These operations retrieve detailed location information pertaining to terminals. GetAllTerminalLocations retrieves data for all terminals. Meanwhile, GetSpecificTerminalLocation is passed a TerminalID, or unique terminal identifier, as part of the TerminalMsg parameter for cases when only a specific terminal is required. A valid API Access Code from the WSDOT Traveler API must be provided.
Please consider using GetCacheFlushDate() to coordinate the caching of this data in your application.
These operations reflect terminal condition data (the number of drive-up and reservation spaces available for select departures). GetAllTerminalSailingSpace retrieves data for all terminals. Meanwhile, GetSpecificTerminalSailingSpace is passed a TerminalID, or unique terminal identifier, as part of the TerminalMsg parameter for cases when only a specific terminal is required. A valid API Access Code from the WSDOT Traveler API must be provided.
This data changes very frequently (potentially every 5 seconds). Please do not cache results in your application for an extended period of time.
These operations provide helpful information for terminal commuters (including parking notes, vehicle-specific tips, etc). GetAllTerminalTransportationOptions retrieves data for all terminals. Meanwhile, GetSpecificTerminalTransportationOption is passed a TerminalID, or unique terminal identifier, as part of the TerminalMsg parameter for cases when only a specific terminal is required. A valid API Access Code from the WSDOT Traveler API must be provided.
Please consider using GetCacheFlushDate() to coordinate the caching of this data in your application.
These operations retrieve highly detailed information pertaining to terminals. They 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:
GetAllTerminalBasicDetails()
GetSpecificTerminalBasicDetail(TerminalMsg)
GetAllTerminalBulletins()
GetSpecificTerminalBulletin(TerminalMsg)
GetAllTerminalLocations()
GetSpecificTerminalLocation(TerminalMsg)
GetAllTerminalTransportationOptions()
GetSpecificTerminalTransportationOption(TerminalMsg)
GetAllTerminalWaitTimes()
GetSpecificTerminalWaitTime(TerminalMsg)
GetAllTerminalVerboseDetails retrieves data for all terminals. Meanwhile, GetSpecificTerminalVerboseDetail is passed a TerminalID, or unique terminal identifier, as part of the TerminalMsg parameter for cases when only a specific terminal is required. A valid API Access Code from the WSDOT Traveler API must be provided.
Please consider using GetCacheFlushDate() to coordinate the caching of this data in your application.
These operations retrieve tips and wait time conditions for both vehicles and walk-on passengers. GetAllTerminalWaitTimes retrieves data for all terminals. Meanwhile, GetSpecificTerminalWaitTime is passed a TerminalID, or unique terminal identifier, as part of the TerminalMsg parameter for cases when only a specific terminal is required. A valid API Access Code from the WSDOT Traveler API must be provided.
Please consider using GetCacheFlushDate() to coordinate the caching of this data in your application.