Turo API & Scraper
The Turo API returns peer-to-peer car-rental listings and pricing as clean JSON.
🤖 Using an AI assistant? Copy this link into ChatGPT / Claude / Cursor — it reads every endpoint and parameter instantly and tells you if this API fits your use case.
The primary search endpoint returns available cars for a location with make, model, year, trim, type, transmission, daily price, rating and trip count — the same inventory Turo's own app shows. You can drill into vehicle.detail, vehicle.pricing and vehicle.features, find similar vehicles, and pull a host's profile, their cars and their reviews. It is built for travel apps, pricing monitors and car-sharing analytics that need live Turo data without maintaining a scraper against its anti-bot layer. One ReefAPI key, one shared credit pool, the standard envelope.
Which Turo action fills which field
The search card and the vehicle.similar card share a field list but not the same populated fields, and picking the wrong action is why a Turo integration ends up with a column full of nulls. Measured on 2026-08-27 across three searches (Los Angeles, Miami, Austin: 180 rows) and one vehicle.similar call for a Tesla Model 3 in Miami. Every cell below is what actually came back, not what the schema allows.
| Field | search | vehicle.similar | Measured value |
|---|---|---|---|
| vehicle_id | populated | populated | 3875502, 1780934 (a JSON number, not a string) |
| price_per_day.amount / .currency | populated | populated | 51.3 / "USD" |
| rating | populated | populated | 5.0 in search, 4.82 in similar |
| review_count | populated | null | 24 in search |
| trip_count | null (180 of 180) | populated | 255 in similar |
| transmission | null | populated | "AUTOMATIC" |
| host{host_id, first_name, url} | null (180 of 180) | populated | a numeric host_id and the owner's given name |
| url | null (180 of 180) | populated | turo.com/us/en/car-rental/united-states/miami-fl/tesla/model-3/1780934 |
| location{city, state, latitude, longitude} | populated | null | Los Angeles / CA / 33.9412 / -118.3709 |
| is_all_star_host | populated | null | true |
Neither action is a superset of the other. If you need host attribution and a listing URL, seed with search for coverage and then call vehicle.similar (or vehicle.detail plus host.profile keyed by host.host_id) for the fields search leaves empty. vehicle_id and host_id come back as plain integers in the payload, but every parameter accepts them as strings.
Real request and response JSON
Captured from the indexed primary action, search, on .
{
"method": "POST",
"url": "https://api.reefapi.com/turo/v1/search",
"headers": {
"x-api-key": "$REEF_KEY",
"content-type": "application/json"
},
"body": {
"location": "Miami, FL, USA"
}
}{
"ok": true,
"meta": {
"api": "turo",
"endpoint": "search",
"mode": "live",
"latency_ms": 3435.6,
"record_count": 60,
"bytes": 204041,
"cache_hit": false,
"stop_reason": "limit_reached",
"total_hits": 5614,
"search_location": "MIA - Miami International Airport",
"page": 1,
"has_more": true,
"next_page": 2,
"search_id": "Td5YLYm7",
"charged_credits": 1,
"version": "1.0.0"
},
"data": {
"cars": [
{
"vehicle_id": 3847161,
"make": "Volkswagen",
"model": "Taos",
"year": 2026,
"trim": null,
"type": "SUV",
"fuel_type": null,
"transmission": null,
"price_per_day": {
"amount": 34.2,
"currency": "USD"
},
"rating": 5,
"review_count": 4,
"trip_count": null,
"is_all_star_host": false,
"is_new_listing": null,
"image": "https://images.turo.com/media/vehicle/images/Bi09XGDWSYOiXPXq4dueJQ.jpg",
"location": {
"city": "Hialeah",
"state": "FL",
"country": "US",
"latitude": 25.81881218957484,
"longitude": -80.25968842088261
},
"host": null,
"url": null
},
{
"vehicle_id": 3032840,
"make": "BMW",
"model": "X3",
"year": 2018,
"trim": null,
"type": "SUV",
"fuel_type": null,
"transmission": null,
"price_per_day": {
"amount": 42.78,
"currency": "USD"
},
"rating": 4.9,
"review_count": 127,
"trip_count": null,
"is_all_star_host": false,
"is_new_listing": null,
"image": "https://images.turo.com/media/vehicle/images/ZbHC-tEUQ-eik6NEnrCinw.jpg",
"location": {
"city": "Miami",
"state": "FL",
"country": "US",
"latitude": 25.812123812665998,
"longitude": -80.24640720494887
},
"host": null,
"url": null
},
{
"vehicle_id": 2793326,
"make": "Chevrolet",
"model": "Equinox",
"year": 2024,
"trim": null,
"type": "SUV",
"fuel_type": null,
"transmission": null,
"price_per_day": {
"amount": 41.58,
"currency": "USD"
},
"rating": 4.95,
"review_count": 111,
"trip_count": null,
"is_all_star_host": true,
"is_new_listing": null,
"image": "https://images.turo.com/media/vehicle/images/JxJPFIAeQeqGp8ozELj53g.jpg",
"location": {
"city": "Miami",
"state": "FL",
"country": "US",
"latitude": 25.811614257770877,
"longitude": -80.24743153996553
},
"host": null,
"url": null
}
]
}
}What the Turo API does
| Action | Description | Concrete use case | Key params |
|---|---|---|---|
| search | Search Turo for rentable cars at a location and date range. Filter by make, model, vehicle type (CAR/SUV/MINIVAN/TRUCK/VAN), max price and sort order; paginated (~200 cars/page). Returns the full result page as clean JSON. (If the site serves a bot check the engine retries and, only if it still cannot pass, returns a clean TARGET_BLOCKED — never fabricated data.) | Travel apps call search to search Turo for rentable cars at a location and date range. | location, start_date, end_date, start_time, end_time, ... |
| vehicle.detail | Full detail for one Turo car: make/model/year/trim, transmission, seats, doors, luggage and fuel/battery specs, the categorized feature list, host card, ratings, and the price calendar. The protected listing card (host card + sub-ratings) rides a -guarded endpoint (best-effort, bounded retry); the specs, feature list and price calendar always come back from the open endpoints. | Pricing monitors call vehicle.detail to get full detail for one Turo car. | vehicle_id, start_date, end_date, start_time, end_time |
| vehicle.features | Specs + the full categorized feature list for one car (transmission, seats, doors, luggage capacity, fuel type, battery range, and features like Backup camera, All-wheel drive, Apple CarPlay, grouped by category). | Itinerary products call vehicle.features to get specs + the full categorized feature list for one car (transmission, seats, doors, luggage ca…. | vehicle_id |
| vehicle.pricing | Daily price calendar for one car across a date window: per-day price + day of week. Defaults to the next ~3 months if no window is given. | Hospitality analysts call vehicle.pricing to get daily price calendar for one car across a date window. | vehicle_id, start_date, end_date |
| vehicle.similar | Cars similar to a given make/model near a location and dates — a make/model-seeded list of rentable Turo cars (price, rating, host, photo, location), and the most dependable way to get one. Pass make + model + location; vehicle_id is optional (used only to exclude that exact car). | Travel apps call vehicle.similar to get cars similar to a given make/model near a location and dates. | make, location, model, vehicle_id, start_date, ... |
| host.profile | Full Turo host (driver) profile: first name, All-Star/Pro status, member-since, response rate & time, ratings from renters and from car owners, rental counts and account verifications (phone/email/ID). Last name only with include_pii=true. | Pricing monitors call host.profile to get full Turo host (driver) profile. | host_id |
| host.cars | Every car a Turo host has listed, paginated — make/model/year, daily price, rating, review count, location and photo per car. | Itinerary products call host.cars to get every car a Turo host has listed, paginated. | host_id, page |
| host.reviews | Reviews left for a Turo host by their guests, paginated — star rating, the review text, date and the host's reply. Reviewer first name is kept (public on Turo); last name only with include_pii=true. | Hospitality analysts call host.reviews to get reviews left for a Turo host by their guests, paginated. | host_id, page, per_page |
| location.autocomplete | Resolve a free-text place into Turo search locations (cities and airports) with id, type and coordinates — handy to confirm the place before searching. | Travel apps call location.autocomplete to resolve a free-text place into Turo search locations (cities and airports) with id, type and…. | location |
| makes | The full list of car makes Turo supports in a market (e.g. Tesla, BMW, Toyota, Ferrari) — useful as the allowed values for the search `make` filter. | Pricing monitors call makes to get the full list of car makes Turo supports in a market (e.g. | country |
Call search from your stack
curl -X POST https://api.reefapi.com/turo/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"location":"Miami, FL, USA"}'import requests
r = requests.post(
"https://api.reefapi.com/turo/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"location": "Miami, FL, USA"
},
)
print(r.json()["data"])const res = await fetch("https://api.reefapi.com/turo/v1/search", {
method: "POST",
headers: {
"x-api-key": process.env.REEF_KEY,
"content-type": "application/json",
},
body: JSON.stringify({
"location": "Miami, FL, USA"
}),
});
const { ok, data, meta, error } = await res.json();Ask your MCP-connected assistant: call reefapi.turo.search with {"location":"Miami, FL, USA"}.Who uses this API and why
- Travel and pricing apps call search to compare daily car-rental rates by city and vehicle type.
- Market analysts use host.cars and host.reviews to study top hosts' fleets and ratings.
- Fleet and pricing tools pull vehicle.pricing to benchmark dynamic daily rates for a specific car.
Questions developers ask before integrating
Why are host, url and trip_count null in Turo search results?
The search surface returns a compact card: vehicle_id, make, model, year, type, price_per_day, rating, review_count, location and image. Across 180 rows measured on 2026-08-27 in Los Angeles, Miami and Austin, host, url, trip_count and transmission came back null on every one. They are not missing on Turo's side, they are simply not on that card. vehicle.similar returns host{host_id, first_name, url}, transmission and trip_count for the same kind of listing, and host.profile plus vehicle.detail fill in the rest once you have an id.
Is price_per_day what a renter would actually pay?
No, it is a daily rate and nothing else. For vehicle 3875502 over 2026-09-09 to 2026-09-12, search returned price_per_day.amount 51.30 USD while vehicle.pricing for the same car and the same window listed 58, 62, 70 and 73 USD per day with average_price 65.08 and price_range 58 to 74. Those are two different views of one listing, so pick one and stay consistent. Nothing in the response carries a trip fee, protection plan, delivery charge, young-driver fee or tax line, so you cannot reconstruct a checkout total from this API.
What does card_blocked: true mean on vehicle.detail?
vehicle.detail assembles its answer from more than one surface. The specs (transmission, seats, doors, luggage, fuel_type, fuel_economy) and the categorized feature list always come back. The listing card carrying the host block and the sub-ratings is best-effort. When it cannot be read, the response still returns ok: true with card_blocked: true, meta.stop_reason "card_blocked" and a reduced meta.completeness_pct, 60.0 on the call measured on 2026-08-27. The specs and features in that response are complete and correct. Retry for the card, or fetch the host separately with host.profile.
Why did host.cars return an empty list for a host with hundreds of trips?
host.cars lists the cars a host has live right now, not the cars they have ever rented out. Measured on 2026-08-27, host 33962137 reported rentals_from_renters 202 and ratings_from_renters_count 193 through host.profile, while host.cars returned zero cars with total_pages 0 and has_more false. That is a real answer rather than an error: ok stays true and meta.record_count is 0. A host who has paused or delisted every vehicle looks exactly like this.
How does the Turo location parameter get resolved, and can it land somewhere unexpected?
Free text is resolved to a Turo place, and it can snap to an airport instead of the city you typed. "Los Angeles, CA, USA" came back as meta.search_location "LAX - Los Angeles International Airport", while "Miami, FL" came back as "Miami, FL, USA". Read meta.search_location before trusting a result set. To resolve first, call location.autocomplete: its id is a Google Place ID such as "ChIJEcHIDqKw2YgRZU-t3XHylv8", type is "city" or "airport", and in the measured response city rows had null latitude and longitude while airport rows carried real coordinates.
Do the Turo search filters really narrow the result set?
Yes, they are applied on Turo's side rather than after the fact. A Miami search with vehicle_type SUV, max_price 150 and sort PRICE_LOW returned 60 of 60 rows typed SUV, priced 24.44 to 32.01 USD per day, with meta.total_hits 3,187. The vehicle_type vocabulary is CAR, SUV, MINIVAN, TRUCK, VAN, CARGO_VAN and BOX_TRUCK. Watch for typos: an unrecognized filter value is ignored rather than rejected, so a misspelled vehicle_type quietly hands you the unfiltered market. Page with page until meta.has_more is false; a page is roughly 60 cars.
What is the difference between rating, review_count and trip_count?
rating is the star average, review_count is how many written reviews the car has, and trip_count is how many trips it has completed. They rarely line up, and they do not all appear on the same action. Measured on 2026-08-27, a search row showed rating 5.0 with review_count 24 and trip_count null, while a vehicle.similar row showed rating 4.82 with trip_count 255 and review_count null. host.profile separates them further: rentals_from_renters 202 against ratings_from_renters_count 193, plus rating_from_renters 5.0 rounded and rating_to_hundredth 4.97 for the precise figure.
Where do I get a Turo vehicle_id and host_id if all I have is a URL?
Both are the trailing number in the URL. A car sits at turo.com/us/en/car-rental/united-states/<city>/<make>/<model>/<vehicle_id>, which is how 1780934 was read off the measured Miami Model 3. A host sits at turo.com/us/en/drivers/<host_id>, which is where 33962137 came from. The payload returns both as JSON numbers, but vehicle_id, host_id and their aliases (vehicleId, id, driverId, driver_id) all accept strings, which is the safer choice for large ids in JavaScript.
What is the Turo API?
Turo API is a ReefAPI endpoint group for turo It returns live JSON through POST requests under /turo/v1.
Is the Turo API free to try?
Yes. ReefAPI starts with 1,000 free credits, no card required. Turo calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Turo login or account?
No login to Turo is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Turo data?
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Turo API use?
Turo actions currently cost 1 credit per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call Turo from an AI assistant or MCP client?
Yes. Connect ReefAPI once through MCP and your assistant can call turo actions with the same key, credit pool and JSON envelope used by normal REST requests.