The truck parking data API. Every space, one feed.
Argus aggregates every class of truck parking data in the US into one normalized API: state TPIMS sensor networks, camera AI occupancy counts, rest areas and truck stops, reservable lots from partners like Truck Parking Club, secure yards, and overnight friendly retail lots. Real time availability where it exists, honest static data where it does not.
Six source classes. One normalized record.
Truck parking data is fragmented across state programs, private platforms, and static POI databases. Integrating them one at a time is months of work per source. Argus does the aggregation, deduplication, and trust ranking so you integrate once.
State sensor networks
MAASTO TPIMS across eight states plus Florida TPAS. In ground sensors reporting exact open space counts, the highest trust tier in the feed.
Camera AI counts
Computer vision on curated, lot facing cameras counts open spaces where no sensor exists. Every count ships with a confidence score.
State DOT and operator data
Rest areas, welcome centers, weigh stations, and service plazas from state feeds, with capacity, open status, and facility detail.
Partner inventory
Reservable spaces from Truck Parking Club and secure yard and storage partners, so bookable capacity appears next to public capacity.
Overnight friendly retail
Walmart and other retail lots, filtered to locations with a verified overnight policy. Unknown policy is labeled unknown, never assumed.
National static base
25,000+ mapped truck parking locations from Overture, POI Factory, and OSM, deduplicated so each physical site appears exactly once.
Built for apps that route real drivers
Every site carries a stable, source prefixed ID, truck space capacity, live availability or an honest band, overnight policy, and a data_state field that tells you exactly how much to trust the number. Multi lot facilities roll up. Duplicate records across sources merge into one canonical location with full provenance.
- Counts older than 15 minutes are suppressed, never served as live.
- Trust ranking per site: sensor first, then camera AI, then operator and static data.
- Cross source dedup, so the same physical lot never appears four times.
{
"id": "tpims:WI00039IS0011300SRSTARE11",
"name": "Portage Rest Area #11",
"lat": 43.428772, "lon": -89.483492,
"state": "WI", "highway": "I-39/90/94",
"facility_type": "rest_area",
"capacity": 68,
"available": 55,
"trend": "filling",
"data_state": "live",
"source_trust": "sensor",
"policy": { "allows_overnight": true, "is_24hr": true },
"last_updated": "2026-08-27T14:36:10Z"
}Four endpoints cover the whole job
GET /locationsSearch the national base by bounding box, state, or facility type. Static sites included, so your map is never empty.
GET /locations/{id}One site with current availability, capacity, policy, and provenance.
GET /availabilityFresh sensor and camera readings only, with delta polling for real time inventory sync.
GET /corridorParking along a route polyline, ordered by route mile. Built for navigation and dispatch.
REST with JSON and GeoJSON responses. Bulk CSV snapshots and webhook push feeds are available for high volume integrations.
TPIMS, unified
The MAASTO TPIMS program publishes real truck parking sensor data, but getting it means a different process in every state. This is what integrating TPIMS looks like today:
| State program | How you get the feed today |
|---|---|
| Kentucky, Minnesota | Open feed URLs, no registration |
| Iowa, Michigan, Wisconsin | Email a state contact and request access |
| Kansas | Register through a state portal |
| Indiana, Ohio | Data currently not published |
| Florida TPAS | Separate program, separate schema |
Or call one Argus endpoint. We handle state registrations, schema differences, freshness gates, and the join to a national location base, so TPIMS becomes one integration instead of nine.
Get the full API documentation
The complete reference, schema, coverage detail, and a sample data extract arrive by email within one business day. Design partner slots are open now.
Truck parking data, answered
Where can I get truck parking availability data?
Individual state DOTs publish TPIMS sensor feeds, Florida runs TPAS, and private lots sit behind reservation platforms, so no single public source covers the country. The Argus Truck Parking API aggregates all of them, state sensor networks, camera AI counts, rest area data, truck stops, reservable lots, and overnight friendly retail lots, into one normalized feed with a stable ID per physical location.
What is TPIMS and which states publish truck parking sensor data?
TPIMS is the Truck Parking Information Management System, a MAASTO program where in ground sensors count open truck spaces at public facilities across Iowa, Indiana, Kansas, Kentucky, Michigan, Minnesota, Ohio, and Wisconsin. Florida runs a similar system called TPAS. Argus ingests these feeds, applies freshness and trust gates, and joins them to a national location base so you integrate once instead of nine times.
Is the truck parking availability data real time?
Sensor and camera readings are polled continuously and anything older than 15 minutes is suppressed rather than served stale. Every record carries a data_state field that says whether a site is live, stale, sensor free, or static only, so your app always knows the difference between no sensor here and sensor went quiet.
Do you cover private truck stops and travel centers?
Yes. The location layer includes truck stops, travel centers, rest areas, welcome centers, weigh stations, service plazas, reservable yards, and retail lots that verifiably allow overnight truck parking. Live counts attach where a sensor or curated camera covers the lot, and every location ships with capacity and policy fields where known.
Can I get truck parking data as a CSV or bulk download?
Yes. Alongside the REST API we deliver bulk snapshots as CSV or GeoJSON and webhook push feeds for high volume integrations. Request the documentation and tell us which delivery format fits your stack.
How accurate is crowdsourced truck parking data compared to cameras and sensors?
Crowdsourced status is a driver tapping a button, often hours old by the time you read it. In ground sensors count actual spaces, and camera AI counts what the lot camera sees right now, each with a timestamp and a trust field. Argus ranks every reading by source class, sensor first, then camera AI, then operator and static data, so your app can show the measurement, not the rumor.
How many truck parking spaces are there in the US?
Federal surveys count roughly 313,000 truck parking spaces nationwide, about one space for every 11 drivers, which is why availability data matters more than another map of locations. Argus maps 25,000+ parking locations and attaches live counts wherever a sensor or curated camera covers the lot.
How is this different from a parking reservation platform?
Reservation platforms show only their own bookable inventory. Argus is the data layer underneath: public and private, reservable and first come first served, sensor counted and camera counted, in one schema. We partner with reservation platforms like Truck Parking Club rather than compete with them.
How do I get API access and what does it cost?
Documentation is free and arrives by email within one business day of requesting it below. Standard API keys, bulk snapshot delivery, and data partnership terms are priced by volume and use case. Design partner slots are open now.