Apply for Turo API access through the Turo developer program; the API is partner-gated and requires approval before credentials are issued.
Authenticate using OAuth 2.0 with your client credentials to obtain a bearer token scoped to the actions your integration requires.
Search for available vehicles by sending a request with location coordinates, radius, start time, and end time to the vehicle search endpoint.
Choose a vehicle from the results and retrieve its detail page to confirm pricing, trip fee breakdown, protection plan options, and cancellation policy.
Create a trip booking request with the selected vehicle ID, trip dates, guest details, and chosen protection plan; capture the trip ID from the response.
Monitor the trip state via polling or webhook: the host must accept the request before the booking is confirmed; handle declined or expired requests gracefully.
Known gotchas
Turo charges a trip fee on top of the daily rate; display the total-cost breakdown (daily rate + trip fee + protection plan) to users before they confirm.
Vehicle availability can change between search and booking; always check for a conflict or unavailability error on the booking response and prompt re-search.
Turo's API is not publicly documented; all endpoint paths and schemas in this route are subject to change — rely on official partner documentation received post-approval.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp