Reference · built on requestCommons signalTransit, roads & mobility

WSDOT Traveler Information API

Traffic flow, travel times, highway alerts, mountain passes, border waits, toll rates, and ferries from WSDOT's Traveler Information API.

Request accessPricing ↗

About

The Washington State Department of Transportation publishes its Traveler Information API at wsdot.wa.gov/traffic/api. It groups services for Border Crossings, Bridge Clearances, Commercial Vehicle Restrictions, Highway Alerts, Highway Cameras, Mountain Pass Conditions, Toll Rates, Traffic Flow, Travel Times, Weather Information, Weather Stations, and the WSF Fares, Schedule, Terminals, and Vessels. Each service has JSON and XML methods over HTTP and a WSDL for SOAP. Work zones come separately as WZDx v4.2 feeds.

Through Fibric, an operator reads flow stations, travel time routes, and alerts along the corridors you name, then proposes a change to a delivery window, a shuttle departure, or a route for your approval. Each proposal cites the WSDOT record it came from.

This is a reference listing. It documents what Fibric would read from WSDOT Traveler Information API and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Traffic Flow: GetTrafficFlowsAsJson returns each FlowData station with FlowReadingValue (WideOpen, Moderate, Heavy, StopAndGo), Region, StationName, and Time
  • Travel Times: TravelTimeRoute records with Name, StartPoint, EndPoint, Distance in miles, AverageTime and CurrentTime in minutes, and TimeUpdated
  • Highway Alerts: GetAlerts returns active incidents with EventCategory, Priority, EventStatus, StartTime, EndTime, and roadway locations; SearchAlerts filters by StateRoute, Region, milepost
  • Mountain Pass Conditions: GetMountainPassConditions returns a PassCondition report for every pass; GetMountainPassCondition returns one by PassConditionID
  • Border Crossings: GetBorderCrossings returns current wait times in minutes for crossings into Canada
  • Toll Rates for high occupancy lanes, and Highway Cameras through GetCameras and SearchCameras by StateRoute, Region, and milepost
  • WSF Vessels REST: vessellocations, vesselbasics, vesselhistory, vesselstats, and cacheflushdate; WZDx v4.2 WorkZoneFeed and DeviceFeed

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Re-time a delivery when a pass closes

    A PassCondition report or a Highway Alert on the road ahead lets the operator propose a resequenced stop list for the affected driver. You approve. The record keeps the AlertID.

    With Route Resequence

  • Send a truthful ETA

    CurrentTime on a TravelTimeRoute against AverageTime shows the delay on the corridor. The operator proposes an ETA notice to the customer with the route name and the minutes.

    With ETA Notice

  • Check a toll charge against the posted rate

    The Toll Rates service returns the current high occupancy lane rate. The operator compares a billed charge to the rate at that time and proposes a dispute when they disagree.

    With Toll Dispute

  • Warn arriving guests about a ferry or border wait

    Border Crossings wait minutes and WSF vessellocations feed a proposed shuttle departure change, which a person approves before it goes out.

    With Shuttle Timing

Requirements

  • An Access Code requested with an email address on wsdot.wa.gov/traffic/api; WSDOT uses the address only to notify you of service changes
  • The FlowDataID, TravelTimeID, StateRoute, or milepost ranges for the corridors you care about
  • A polling schedule; the services are request-response and publish no push or webhook
Authentication
A free Traveler API Access Code, issued by email from the API page and passed as the AccessCode query parameter (apiaccesscode for the WSF services).

Limits

  • The API pages state no update interval for flow, travel time, or alert data; only the WZDx feed_info declares update_frequency, at 60 seconds
  • A flow reading is a five-step scale from WideOpen to StopAndGo, not a speed or a volume
  • Bridge clearances are published about three inches under the measured value and WSDOT says they cannot be guaranteed
  • WSDOT provides the data as-is and as available, disclaims warranties, and publishes no reuse licence on the API pages

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request WSDOT Traveler Information API ↗

Questions and answers

Do I need a key to call the Traveler Information API?
Yes. WSDOT assigns an Access Code when you enter an email address on the API page. Every method takes it as AccessCode; the WSF services take apiaccesscode. WSDOT says the address is used only to notify you of service changes.
What does a traffic flow reading contain?
A FlowData record: FlowDataID, StationName, Region, FlowStationLocation, Time, and FlowReadingValue. The reading is an enumeration: 0 Unknown, 1 WideOpen, 2 Moderate, 3 Heavy, 4 StopAndGo, 5 NoData. WSDOT lists coverage for Vancouver, Olympia, Tacoma, Seattle, and Spokane.
How often does the data refresh?
WSDOT states no interval for these services. Each TravelTimeRoute carries TimeUpdated and each Alert a LastUpdatedTime, so you can see the age of a record. The WZDx feeds declare update_frequency 60 in feed_info.
Ask about WSDOT Traveler Information API

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by Washington State Department of Transportation (wsdot.wa.gov). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy