Reference · built on requestCommons signalTransit, roads & mobility

511NY Developer API

Statewide road events, cameras, message signs, alerts, and winter road conditions from NYSDOT's 511NY Developer API in XML or JSON.

Request accessPricing ↗

About

511NY is the traveler information service of the New York State Department of Transportation. Its Developer API is a REST interface with five calls: GetEvents, GetCameras, GetMessageSigns, GetAlerts, and GetWinterRoadConditions. Every call takes a developer key and a format of xml or json in the query string. The help page describes the data as traffic speeds, incidents, roadwork, and cameras for New York, and access is governed by the Developer's Access Agreement, which NYSDOT reviews request by request.

On Fibric, an operator reads the events and winter conditions on the roads your drivers use and proposes a resequenced route, a delivery hold, or a customer ETA message for your approval, with the event record attached.

This is a reference listing. It documents what Fibric would read from 511NY Developer 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

  • GetEvents: every event with EventType among accidentsAndIncidents, roadwork, specialEvents, closures, transitMode, generalInfo, and winterDrivingIndex
  • Event detail fields: RegionName, CountyName, Severity, RoadwayName, DirectionOfTravel, LanesAffected, LanesStatus, StartDate, PlannedEndDate, and LastUpdated
  • GetCameras: each camera's Name, RoadwayName, DirectionOfTravel, image Url, VideoUrl, and Disabled or Blocked flags
  • GetMessageSigns: the Messages currently rotating on each variable message sign, with Roadway and DirectionOfTravel
  • GetAlerts: traffic alerts with Message, Notes, and the AreaNames they apply to
  • GetWinterRoadConditions: a Condition per roadway segment with AreaName, LocationDescription, an encoded Polyline, and LastUpdated in Unix time

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

  • Reroute around a closure before the driver reaches it

    Poll GetEvents and keep the closures and accidentsAndIncidents on today's roadways. When one lands ahead of a stop, the operator proposes a resequenced route and cites the event ID.

    With Route Resequence

  • Hold upstate deliveries on a winter condition

    Read GetWinterRoadConditions for the segments your runs cross. When a Condition on the route crosses your rule, the operator proposes holding the affected orders and drafts the notice.

    With Weather Hold

  • Send an ETA that names the incident

    Match the driver's roadway to open events. When a roadwork or incident overlaps the remaining route, the operator proposes a customer ETA message quoting the Description field.

    With ETA Notice

Requirements

  • A 511NY account, then an API key request that the help page says shows on the same page once issued
  • A brief description of your intended service or product; the Developer's Access Agreement says requests are reviewed case by case
  • Request pacing within the throttle of 10 calls every 60 seconds
  • A parser for either XML or JSON, chosen per call with format=xml or format=json
Authentication
A free developer key requested from a registered 511NY account, passed as key={developerKey} in the query string of every call.

Limits

  • Throttling is enabled at 10 calls every 60 seconds, and each call returns the whole statewide set with no filter parameters
  • Event dates use dd/MM/yyyy HH:mm:ss strings, while winter road conditions use Unix time; the LcsEntries field is documented as not used
  • The access agreement warns that availability and accuracy can change as often as daily and that posted restrictions supersede the feed
  • Branding rules apply: 511NY may only be acknowledged with the approved tag line, logo, or banner, never altered or implying endorsement

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 511NY Developer API ↗

Questions and answers

What does a call look like?
A GET to https://511ny.org/api/getevents?key={key}&format={format}, with the same shape for getcameras, getmessagesigns, getalerts, and getwinterroadconditions. Both key and format are required; format accepts xml or json. Responses come back as application/xml or application/json arrays.
Is there a rate limit?
Yes. The help page states that throttling is enabled at 10 calls every 60 seconds. The Developer's Access Agreement adds that there is no fee for the real-time and static data feed.
May I redistribute the data?
The Developer's Access Agreement allows a Data Disseminator to redistribute, enhance, repackage, or add value to the data, provided the integrity of the source data is preserved and not altered. It encourages the tag line powered by 511NY and sets rules for logo use.
Ask about 511NY Developer 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 New York State Department of Transportation, 511NY (511ny.org). 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