Reference · built on requestCommons signalTransit, roads & mobility

National Highways WebTRIS

Traffic counts and average speeds from National Highways roadside sites in England, as daily, monthly, and annual reports without a key.

Request accessPricing ↗

About

WebTRIS is the traffic information service National Highways runs for the strategic road network in England. It holds counts from MIDAS, TMU, and TAME inductive-loop sites and from legacy TRADS sites. The API at webtris.nationalhighways.co.uk/api serves sites, areas, site types, daily, monthly, and annual reports, and data quality figures. A daily report row covers a 15-minute period and carries volume in four vehicle-length classes, counts by speed band, average mph, and total volume.

Through Fibric, an operator reads the count sites near your depots or stores and proposes service windows, staffing, or benchmarks from measured flow. Each proposal names the site and the date range it used.

This is a reference listing. It documents what Fibric would read from National Highways WebTRIS 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

  • Sites through /v1.0/sites and /v1.0/sites/{site_Ids}: Id, Name, Description, Longitude, Latitude, and Status (Active or Inactive)
  • Site types through /v1.0/sitetypes: 1 MIDAS, 2 TAME, 3 TMU, 4 Legacy; /v1.0/sitetypes/{siteType_Id}/sites lists the sites of one type
  • Daily, Monthly, and Annual reports through /v1.0/reports/{report_type} with sites, start_date, end_date (ddmmyyyy), page, and page_size
  • Per 15-minute row: Time Period Ending, counts for 0-520 cm, 521-660 cm, 661-1160 cm, and 1160+ cm, speed bands, Avg mph, Total Volume
  • Areas through /v1.0/areas and /v1.0/areas/{area_Ids}
  • Data quality through /v1.0/quality/overall and /v1.0/quality/daily: minutes of data received as a share of the range

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

  • Set service windows from measured flow

    Daily reports for the sites on a customer's approach road show when Total Volume peaks. The operator proposes appointment windows that avoid those periods and records the site and dates it used.

    With Service Window

  • Benchmark sites by road traffic

    Annual volumes at the nearest count point give each store or depot an external traffic figure. The operator proposes a like-for-like grouping for your review.

    With Site Benchmark

  • Plan a run by time of day

    Fifteen-minute profiles for the motorway links on a run show where an earlier or later start saves time. The operator proposes a departure change for your approval.

    With Route Resequence

  • Add road traffic to the demand outlook

    Monthly reports for the links serving a site sit beside your own history in the outlook. The operator flags where the two diverge and says which months it read.

    With Demand Outlook

Requirements

  • The site Ids for the count points you need, taken from /v1.0/sites or the map view
  • Dates in ddmmyyyy form and paging with page and page_size; the report Header carries a nextPage link
  • Tolerance for lag: sensor data is usually processed and uploaded a month in arrears
Authentication
None. The API page states that all WebTRIS API endpoints are available without registration or API keys.

Limits

  • New monthly data is paused while National Highways changes the underlying infrastructure; the rolling ten-year history stays available
  • Data arrives about a month in arrears, so this is a planning and benchmarking source, not a same-day one
  • Speed-band columns can be empty for a site while the length classes, Avg mph, and Total Volume are filled
  • The site carries no licence page; the data.gov.uk record for the network journey time and traffic flow data lists the UK Open Government Licence

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 National Highways WebTRIS ↗

Questions and answers

Is a key needed to use the WebTRIS API?
No. The API page states that all WebTRIS API endpoints are available without registration or API keys. Dates go in ddmmyyyy form, and reports are paged with page and page_size. Site type ids are 1 MIDAS, 2 TAME, 3 TMU, and 4 Legacy.
What is in a daily report row?
One row per 15-minute period per site: Site Name, Report Date, Time Period Ending, Time Interval, counts by vehicle length (0-520 cm, 521-660 cm, 661-1160 cm, 1160+ cm), counts by speed band, Avg mph, and Total Volume. One day returns 96 rows.
How current is the data?
Not current. The FAQ says sensor data is usually processed and uploaded a month in arrears. In September 2026 National Highways paused new monthly data for around three to four months while it changes the service's infrastructure; the rolling ten-year history remains available.
Ask about National Highways WebTRIS

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 National Highways (webtris.nationalhighways.co.uk). 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