# INRIX

> INRIX turns anonymized GPS probe data from connected vehicles, mobile devices and fleets into
> real-time and historical road intelligence for automakers, cities, departments of transportation,
> retailers and app developers. Its developer surface is organized around the INRIX IQ platform and
> documented at docs.inrix.com. Every product API is gated by a single bearer access token minted by
> the INRIX User Accounts System (UAS).

Generated by the API Evangelist enrichment pipeline on 2026-08-01. INRIX does not publish an
llms.txt of its own; this file was generated from the INRIX documentation and the three
machine-readable contracts INRIX serves.

## Getting started

- [Getting Authorized](https://docs.inrix.com/authentication/getting_authorized/): the UAS appToken flow — SHA-1 of "appId|appKey", then a bearer token
- [Documentation home](https://docs.inrix.com/): the full INRIX product documentation tree
- [INRIX for Developers](https://inrix.com/developers/): Traffic, Analytics and Parking product overview
- [INRIX IQ console](https://iq.inrix.com/): registration, trial, key management and the data downloader
- [Best practices](https://docs.inrix.com/reference/bestpractices/): ISO 8601 datetime conventions
- [Glossary](https://docs.inrix.com/reference/glossary/): INRIX traffic terminology
- [Error status IDs](https://docs.inrix.com/reference/errorstatusids/): the 360-entry statusId registry shared across products
- [Status](https://status.inrix.com/): INRIX IQ service status

## Machine-readable contracts

- [INRIX User Accounts System (UAS)](https://uas-api.inrix.com/swagger/docs/v1): Swagger 2.0, 83 operations — tokens, applications, developers, users, user groups, devices
- [INRIX Parkme API](https://parking-api.inrix.com/api/swagger.json): Swagger 2.0 — the public parking subset
- [INRIX Signals Analytics API](https://signals-api.inrix.com/openapi.json): OpenAPI 3.0.1 — intersection metrics, metadata and namespace management
- [UAS Swagger console](https://uas-api.inrix.com/swagger): interactive
- [INRIX Parking Services 3.0 reference](https://parking-api.inrix.com/doc/v3/bulk/): HTML object reference for the current parking API

## Traffic APIs

- [General information](https://docs.inrix.com/traffic/general_info/)
- [Segment Speed](https://docs.inrix.com/traffic/segmentspeed/): https://segment-api.inrix.com/v1/segments/speed — real-time, historical and predicted speeds on XD and TMC segments
- [Safety Alerts](https://docs.inrix.com/traffic/incidents/): https://incident-api.inrix.com/v1/incidents — incidents, construction, flow and hazards
- [Traffic Tiles](https://docs.inrix.com/traffic/tiles/): https://tile-api.inrix.com — quadkey-addressed raster traffic overlays
- [Routing](https://docs.inrix.com/traffic/routing/): traffic-influenced routing with predictive look-ahead
- [Drive Time Polygons](https://docs.inrix.com/traffic/drivetimepolygons/): isochrones from typical traffic patterns
- [Traffic Cameras](https://docs.inrix.com/traffic/trafficcameras/): camera locations and last-captured images
- [Dangerous Slowdowns](https://docs.inrix.com/traffic/dangerousslowdowns/): https://dsd.api.inrix.com/v2/DangerousSlowdowns
- [Fuel Stations](https://docs.inrix.com/traffic/fuel/): https://fuel-api.inrix.com/v1/fuelstations/
- [INRIX TPEG Connect](https://docs.inrix.com/traffic/tpeg/): TISA TPEG delivery for embedded automotive head units

## Parking APIs

- [General information](https://docs.inrix.com/parking/general_info/)
- [Lots (v3)](https://docs.inrix.com/parking/lots-v3/) and [Blocks (v3)](https://docs.inrix.com/parking/blocks-v3/)
- [Occupancy and Probability](https://docs.inrix.com/parking/occupancy/): real-time and historical
- [Parking Filters](https://docs.inrix.com/parking/filters/), [Destinations](https://docs.inrix.com/parking/destinations/), [Bulk](https://docs.inrix.com/parking/bulk/)
- [Change log](https://docs.inrix.com/parking/change_log/)
- [Beta endpoint usage](https://docs.inrix.com/parking/beta/): substitute beta.parkme.com for parkme.com; Stripe test cards

## Analytics and Signals

- [Trade Area Trips](https://docs.inrix.com/analytics/tradeareatrips/): https://trade-areas-api.inrix.com/v1/trips
- [Trip Trends Reports](https://docs.inrix.com/analytics/triptrends/): https://triptrends-api.inrix.com/v1/reports
- [Signal Analytics Metrics](https://docs.inrix.com/signals/signals-metrics/), [Signals Metadata](https://docs.inrix.com/signals/signals-metadata/), [Availability](https://docs.inrix.com/signals/signals-availability/)
- [Roadway Analytics speeds data downloader](https://docs.inrix.com/ra/speedsdatadownloader/): https://roadway-analytics-api.inrix.com/v1/data-downloader

## Data in and out

- [Data Download Service](https://docs.inrix.com/datadownload/datadownload/): https://mapdata.inrix.io/v1/datadownload — map releases, XD network deltas, OpenLR dictionaries, shapefiles, GeoJSON
- [GPS Data Stream](https://docs.inrix.com/sendingdata/gpsdatastream/): https://appsvc-ingest.inrix.io/v1/gpsdatastream
- [Parking Events Data Stream](https://docs.inrix.com/sendingdata/parkdatastream/): https://appsvc-ingest.inrix.io/v1/parkdatastream
- [XFCD data stream](https://docs.inrix.com/traffic/datastream/): https://appsvc-ingest.inrix.io/v1/datastream

## Reference

- [Dynamic Location Referencing](https://docs.inrix.com/reference/dynamiclocationreferencing/): XD, TMC, OpenLR
- [INRIX Segments](https://docs.inrix.com/reference/getsegments/), [Geographies](https://docs.inrix.com/reference/geographies/), [Map version](https://docs.inrix.com/reference/mapversion/)
- [Logo usage rules](https://docs.inrix.com/reference/inrixlogousagerules/)
- [Support](mailto:support@inrix.com)

## SDKs

- [SDK overview](https://docs.inrix.com/sdk/general/)
- [INRIX-iOS-ClientLibrary](https://cocoapods.org/pods/INRIX-iOS-ClientLibrary): CocoaPods
- [INRIX SDK Core for Android](https://inrix.jfrog.io/inrix/sdk-releases/com/inrix/sdk/core/): Gradle, v9.0, gated Artifactory
- [SDK release notes](https://docs.inrix.com/sdk/releasenotes/)
- [INRIX on GitHub](https://github.com/INRIX)

## Conventions an agent should know

- Errors carry a numeric `statusId` plus `statusText` alongside the HTTP status; `statusId: 0` is success. INRIX does not use RFC 9457 problem+json.
- The access token goes in either `Authorization: Bearer {token}` or an `accessToken` query parameter. Cache it until near expiry.
- Tokens are not interchangeable between production, beta, sandbox and qa hosts.
- Geospatial queries are bounded by `box`, `point` + `radius` or a `segmentSet`; oversized queries return statusId 153 or 154.
- Timestamps are ISO 8601 (`Z` or `+hh:mm`), except the data-upload streams which take a UNIX timestamp in `ts`.
- INRIX documents no idempotency key, no rate-limit headers, no webhooks, no AsyncAPI, and no MCP server.

## Legal

- [Site terms](https://inrix.com/site-terms/)
- [Site privacy policy](https://inrix.com/site-privacy-policy/): includes the EU-U.S. Data Privacy Framework certification
- [Cookie policy](https://inrix.com/site-cookie-policy/)