Register as a ParkWhiz partner to obtain API credentials; production credentials are separate from sandbox credentials available at api-sandbox.parkwhiz.com/v4/
Authenticate using your API key in request headers as described in the ParkWhiz v4 documentation; the API uses REST with JSON responses and standard HTTP verbs
GET parking options by sending a search request with destination coordinates or address, arrival and departure datetimes, and optional radius parameter
Parse the response for location ID, rate, availability status, amenities, and vehicle height restrictions before presenting choices to the traveler
POST to the bookings endpoint with the selected location rate ID and driver details to create a confirmed parking reservation; capture the booking token returned
Use the booking token to retrieve, modify if the provider allows, or cancel the reservation; monitor for availability updates via the Management API data feeds if operating as a supply-side partner
Known gotchas
The sandbox API at api-sandbox.parkwhiz.com/v4/ behaves differently from production in terms of available inventory; test coverage may not reflect real-world edge cases such as sold-out lots or rate changes
Vehicle height restrictions are returned per location and must be surfaced to the traveler; booking a location incompatible with the vehicle dimensions results in on-site denial without a refund path
Rate IDs have validity windows; if the user takes too long to confirm, the rate may expire and a fresh search is required before a new booking attempt
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