canonical: https://jentic.com/apis/511on.ca/511on

# 511on Ca Ontario 511 Transportation API

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.

## For AI 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.

## Scope

Does not handle navigation routing, mapping tiles, or roads outside Ontario - use for live Ontario provincial highway data only.

## Capabilities

- 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
- Look up ferry departure schedules and operating status for provincial ferry crossings
- Find carpool lots, service centres, and truck inspection stations along a planned route

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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 |

## Key resources

- **Events** — Active traffic incidents and special events on Ontario highways
- **Construction** — Scheduled and active highway construction projects
- **Cameras** — Live traffic camera image URLs across the province
- **Road Conditions** — Current road surface and weather conditions reported by patrols
- **Ferries** — Schedules and operating status for provincial ferry crossings
- **Carpool Lots and Service Centres** — Locations of carpool lots, service centres, and truck inspection stations

## Why Jentic

- **Setup:** Wiring the Ontario 511 Transportation API by hand means managing its API key, appending it as a query parameter, and parsing the v2 highway data feeds yourself. Through Jentic you install once, import the Ontario 511 Transportation API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** This API is read-only and selects data through query parameters rather than a resource id in the path, so limit the agent to the operations it needs, such as reading events, road conditions, or cameras, and leave out others unless you add them. You choose the allowed set, so only the operations you pick can run.
- **Credential handling:** Your Ontario 511 API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get Ontario highway incidents' or 'read Ontario road conditions', and Jentic returns the matching Ontario 511 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **New York 511 API** — Equivalent traffic and travel data API for New York State highways
- **Arizona 511 API** — Arizona Department of Transportation traffic and incident feed
- **TomTom Routing API** — Calculates routes and travel times that can be adjusted using 511 incident data
- **HERE Maps API** — Mapping and traffic flow data covering Ontario alongside global coverage

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

### 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 your Jentic One instance 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.

### Can I limit what my agent is allowed to do with the Ontario 511 Transportation API?

Yes. Because you run Jentic One yourself, your own rules decide which of the read-only Ontario 511 operations the agent may call, so you can allow only what it needs, such as reading events or road conditions, and leave out cameras, ferries, or truck inspection stations. Every operation retrieves data through query parameters rather than modifying anything, so the agent can never write or delete provincial highway records. Only the operations you pick can run, and your Ontario 511 API key is stored encrypted and injected at execution time so it never enters the agent's context.