Ontario 511 Transportation API

Name: Ontario 511 Transportation API API
Brand: Ontario 511 Transportation API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMaps GeolocationRouting DirectionsapiKey16 EndpointsREST

For Agents

Look up live Ontario highway events, road conditions, traffic cameras, and ferry schedules from the official 511 Ontario data feed. Useful for routing agents, fleet dispatch, and travel-planning assistants operating in Ontario.

Quickstart

Get started with Ontario 511 Transportation API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"Ontario highway traffic and road conditions"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Ontario 511 Transportation API API.

Retrieve current traffic events and incidents on Ontario highways with location and severity detail

List active construction projects with scheduled start and end dates

Pull traffic camera image URLs for any monitored Ontario highway segment

Check current road surface and weather conditions reported by maintenance patrols

GET STARTED

Start building with Ontario 511 Transportation API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Ontario 511 Transportation API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Ontario 511 Transportation API, keeping it validated and agent-ready. The Ontario 511 Transportation API exposes real-time provincial traffic and travel data published by the Ontario Ministry of Transportation, including incidents, construction zones, traffic camera feeds, road surface conditions, ferry schedules, carpool lots, transit hubs, service centres, truck inspection stations, and winter maintenance vehicles. The API returns JSON for sixteen GET endpoints scoped to Ontario highways and is intended for navigation apps, fleet operators, and travel planning tools that need authoritative road data. Authentication uses a per-developer API key requested through the Ontario 511 developer portal.

Use Cases

Patterns agents use Ontario 511 Transportation API API for, with concrete tasks.

★ Real-Time Trip Planning for Ontario Drivers

Surface live incident, construction, and road condition data inside a navigation app or driver portal so users avoid closures and slowdowns on Ontario highways. The API exposes events, construction, and roadconditions endpoints that return location-tagged records refreshed by the Ontario Ministry of Transportation, allowing apps to render warnings on a map without scraping public web pages. Integration is typically a half-day for a basic feed and two to three days for full filtering and caching.

Call /get/events and /get/roadconditions, filter records to Highway 401 between Toronto and Kingston, and return any active incidents or poor surface conditions with timestamps.

Fleet Dispatch and Routing Adjustments

Logistics and fleet operators running deliveries through Ontario use the construction, events, and truck inspection station endpoints to reroute vehicles around closures and confirm where commercial vehicle inspections are open. The API covers all provincial highways and is updated continuously, so dispatchers can flag problem corridors before drivers depart. Connecting the feed to an existing dispatch system takes a developer one to two days.

Fetch /get/construction and /get/truckinspectionstations, intersect with a planned route from Windsor to Toronto, and produce a list of zones to avoid plus the next open inspection station.

Public Information Dashboards and Travel Boards

Tourism boards, regional municipalities, and travel publishers embed Ontario 511 data on dashboards showing camera feeds, ferry status, and service centre locations. The cameras and ferries endpoints return image URLs and schedule data ready for direct display, eliminating the need for manual content updates. A typical dashboard build using cached responses takes two to four days.

Pull /get/cameras and /get/ferries, group cameras by region, and render a dashboard component listing the top ten cameras and the next ferry departure for each crossing.

Agent-Driven Ontario Travel Assistant via Jentic

An AI travel assistant connected through Jentic can answer driver questions about Ontario highway conditions in natural language by routing queries to the right 511 endpoint. Jentic returns the operation schema so the agent passes only the API key once and receives structured incident or condition records, with no need to maintain a hand-written client. Setup through Jentic is under thirty minutes versus a half-day of manual integration.

Search Jentic for 'Ontario highway traffic conditions', load the /get/events schema, and answer the user's question 'is there construction on the 401 today' with the live data.

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for ontario 511 transportation api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/get/events

List active traffic events and incidents

GET

/get/construction

List active highway construction zones

GET

/get/cameras

List traffic camera feeds with image URLs

GET

/get/roadconditions

Retrieve current road surface conditions

GET

/get/ferries

List ferry crossings and schedules

GET

/get/carpoollots

List carpool lot locations

GET

/get/truckinspectionstations

List commercial vehicle inspection stations

GET

/get/events

List active traffic events and incidents

GET

/get/construction

List active highway construction zones

GET

/get/cameras

List traffic camera feeds with image URLs

GET

/get/roadconditions

Retrieve current road surface conditions

GET

/get/ferries

List ferry crossings and schedules

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Ontario 511 API keys are stored encrypted in the Jentic vault (MAXsystem) and attached as a query parameter at execution time. Agents never see the raw key in their prompt or tool input.

Intent-based discovery

Agents search Jentic with intents like 'Ontario highway incidents' or 'Ontario road conditions' and receive the matching 511 operation with its input schema, so the agent can call the right endpoint without reading the developer portal.

Time to first call

Direct integration with the Ontario 511 API takes about half a day to register a key, parse the schema, and add caching. Through Jentic the same call is reachable in under thirty minutes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

New York 511 API

Equivalent traffic and travel data API for New York State highways

Choose this when the user needs road conditions or incidents in New York rather than Ontario.

Alternative

Arizona 511 API

Arizona Department of Transportation traffic and incident feed

Choose this for Arizona highway data; use Ontario 511 for Ontario.

Complementary

TomTom Routing API

Calculates routes and travel times that can be adjusted using 511 incident data

Pair with Ontario 511 when an agent needs to compute a route and then check whether it crosses any active incidents.

Complementary

HERE Maps API

Mapping and traffic flow data covering Ontario alongside global coverage

Use HERE for map rendering and broader traffic flow; use Ontario 511 for the official provincial incident and construction feed.

FAQs

Specific to using Ontario 511 Transportation API API through Jentic.

Why is there no official OpenAPI spec for Ontario 511 Transportation API?

The Ontario Ministry of Transportation publishes the 511 service with text-based developer documentation but does not ship a machine-readable OpenAPI specification. Jentic generates and maintains this spec so AI agents and developers can call the API through structured tooling. It is validated against the live endpoints and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Ontario 511 Transportation API use?

The API uses an API key passed as a query string parameter on every request. Keys are issued through the Ontario 511 developer portal. When called through Jentic the key is stored encrypted in the Jentic vault and injected at execution time, so the raw key never enters agent context.

Can I get real-time traffic incidents on Highway 401 with the Ontario 511 Transportation API?

Yes. Call GET /get/events to retrieve all current incidents and filter the response by road name or geographic bounding box for Highway 401. The feed is refreshed continuously by the ministry and includes incident type, location, and severity.

What are the rate limits for the Ontario 511 Transportation API?

The Ontario 511 developer agreement requests that callers cache responses for at least sixty seconds and avoid polling more frequently than the published refresh intervals. There is no published numeric per-second cap; sustained abuse can result in the key being revoked. For production use, cache responses and poll on a one-to-five-minute interval.

How do I check road conditions on a route through Jentic?

After running pip install jentic and configuring JENTIC_AGENT_API_KEY, search Jentic for 'Ontario road conditions', load the /get/roadconditions schema, and execute. Jentic returns the structured records and the agent can intersect them with a planned route. The full search-load-execute flow takes a few seconds.

Does the Ontario 511 Transportation API cover roads outside Ontario?

No. The data is limited to provincial highways and ferry routes operated by or reported to the Ontario Ministry of Transportation. For other Canadian provinces or US states, use the equivalent regional 511 service such as 511ny.org or az511.com.