The Kroozin Stop API
A free, public, unauthenticated JSON API describing this facility: truck parking status, fuel, amenities, and routing. Built for fleet software, ELD platforms, dispatch systems, navigation providers and trucking apps.
https://kroozintruckstop.com/api/v1/ · No API key · No rate
limit · CORS open · Free to redistribute with attribution.
The one rule that matters. A null in this API is a
fact, not a gap. It means NOT MEASURED. Render the accompanying
status field and never substitute a value.
A truck-parking count that is wrong sends a tired driver to a full lot at 2 a.m.
A null sends them somewhere they can actually stop.
Current state, stated plainly
Kroozin is open at I-10 Exit 815. Facility amenities now return
OPEN and appear in the advertisable list. Measured values are a
separate matter: every price returns null and truck parking returns
UNKNOWN, because no occupancy or price feed is commissioned yet. That is the
correct response, not a fault.
The distinction is the whole contract. Capacity is a fact, availability is a
measurement. totalSpaces is publishable the day the concrete cures;
availableSpaces is publishable only while a real observation is under 60
minutes old. Outside that window it returns to null and
freshness reports UNAVAILABLE — never a carried-over number.
Every feed on this page is generated from the canonical location record, so a value can never drift from what the business actually publishes elsewhere.
Endpoints
| Endpoint | Returns |
|---|---|
GET /api/v1/stop | Everything below in one call. Start here. |
GET /api/v1/location | Identity, coordinates, entrances, operational status |
GET /api/v1/fuel | Diesel, DEF, gasoline — status, positions, lane wait, price |
GET /api/v1/truck-parking | Parking status and count |
GET /api/v1/amenities | Every amenity with status, plus the advertisable list |
GET /api/v1/food-status | Food service status and hours |
GET /api/v1/directions | Google / Apple / Waze deep links and the truck entrance |
GET /api/v1/stop-lock-services | Services a driver can plan for right now |
/api/public/truck-parking is a permanent alias, kept for TxDOT and
DriveTexas consumers who integrated against it first.
The fields you have to handle correctly
Amenity status
Every amenity carries one of six values:
PLANNED · UNDER_CONSTRUCTION ·
TESTING · OPEN ·
TEMPORARILY_UNAVAILABLE · CLOSED
Only OPEN may be shown to a driver as available.
/api/v1/amenities returns a pre-computed advertisable
array — use it and omit everything else.
Omit, don't grey out. A greyed-out shower on a dispatcher's screen still reads as "they have showers."
Truck parking
status is one of PLENTY, AVAILABLE,
FILLING_FAST, NEAR_CAPACITY, FULL,
UNKNOWN. availableSpaces is a number or null.
A count is only published when all four hold: the site is operational; the source is a sensor, camera count or gate counter (never a manual count); the observation is under 20 minutes old; and source confidence is at least 0.85.
"availableSpaces": 0 with "status": "FULL" is a real and
expected response. Kroozin reports a full lot honestly — a facility that hides
its full nights is one whose "81 open" nobody believes.
The truck entrance is not the pin
facility.truckEntrance is separate from
facility.latitude/longitude and is currently null with
surveyed: false.
Route commercial vehicles to the display pin until it is populated. I-10 is limited-access here and the street address does not geocode; when the surveyed entrance lands, it will be the difference between a tractor-trailer arriving and being routed past.
Diesel lane wait
NO_WAIT · SHORT_WAIT · BUSY
· UNKNOWN. Bands only — Kroozin does not publish a claimed
minute count. A wrong "4 minute wait" costs the sale and the trust; a band that says
BUSY is right often enough to be useful.
Example
curl https://kroozintruckstop.com/api/v1/stop
{
"apiVersion": "v1",
"facility": {
"id": "KROOZIN_I10_815",
"name": "Kroozin Truck Stop & Travel Center",
"highway": "I-10",
"exit": "815",
"latitude": 29.839034,
"longitude": -94.603414,
"truckEntrance": { "latitude": null, "longitude": null, "surveyed": false }
},
"operational": false,
"operationalStatus": "UNDER_CONSTRUCTION",
"openingYear": 2026,
"truckParking": {
"status": "UNKNOWN",
"totalSpaces": 150,
"availableSpaces": null,
"freeOvernight": true,
"reservedSpaces": 45,
"updatedAt": null
},
"diesel": {
"status": "UNDER_CONSTRUCTION",
"highFlow": true,
"positions": 18,
"lanes": 5,
"laneStatus": "UNKNOWN",
"price": null
}
}
What is here
Kroozin sits at I-10 Exit 815 in Hankamer, Texas — in the middle of the 59-mile stretch between Baytown and Beaumont with no full-service truck stop. Roughly 65,000 vehicles a day pass this point, about 20,700 of them trucks.
- 150+ free overnight truck spaces — lit, camera-covered, staffed overnight
- 18 diesel positions across 5 high-flow lanes, DEF at every lane, truck lanes separate from cars
- Private showers cleaned after every use, laundry, driver lounge, Wi-Fi
- Kroozin BBQ, breakfast tacos and kolaches from 4 a.m., 24/7
- Dedicated truck entrance, separated from automobile and RV flow
Fleet and dispatch platforms: if you can surface this facility to drivers or let a dispatcher insert it as a stop, we want to help you do it and we will fill in whatever fields your schema needs.
Known limits
totalSpacesis 150+, settled 26 Aug 2026. Read it from this endpoint rather than hard-coding it, so a future change propagates.- Truck entrance coordinates are unsurveyed. Use the display pin.
- No occupancy system is installed, so
availableSpaceswill benulluntil one is commissioned.
What Kroozin is not
Kroozin is a private commercial facility. It is not a TxDOT Safety Rest Area and is not operated by, endorsed by, or affiliated with TxDOT. If you display this data alongside state facility data, label Kroozin as a private facility.
Versioning
Breaking changes ship under a new path (/api/v2/). /api/v1/
keeps its contract. Additive fields may appear in v1 without notice, so parse
leniently and ignore unknown keys.