POST /api/google/maps/directions
Price: 30 credits
Get Google Maps routes between two places for a travel mode, with distance, duration and steps.
Get Google Maps directions between an origin and a destination (addresses or place names) by driving, walking, bicycling or transit. Each item is one alternative route with distance, duration, traffic range (driving), departure/arrival and fare (transit) and its segments with turn-by-turn steps. Places with no route between them return an empty list.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)origin string required — Starting point: an address, place name or 'latitude,longitude' (examples: "Griffith Observatory, Los Angeles, CA")destination string required — End point: an address, place name or 'latitude,longitude' (examples: "Santa Monica Pier, Santa Monica, CA")mode string — Travel mode (default: "driving"; one of: "driving", "bicycling", "walking", "transit"; examples: "driving")count integer required — Max number of alternative routes (min: 1)@type string (default: "GoogleDirectionsRoute")mode string nullable (one of: "driving", "bicycling", "walking", "transit")summary string nullabledistance_meters integer nullableduration_seconds integer nullableduration_in_traffic_seconds integer nullableduration_in_traffic_min_seconds integer nullableduration_in_traffic_max_seconds integer nullabledeparture_at integer nullablearrival_at integer nullablefare number nullablefare_currency string nullableorigin object nullable@type string (default: "GoogleDirectionsPlace")name string nullableaddress string nullablefeature_id string nullableplace_id string nullablelatitude number nullablelongitude number nullabledestination object nullable@type string (default: "GoogleDirectionsPlace")name string nullableaddress string nullablefeature_id string nullableplace_id string nullablelatitude number nullablelongitude number nullablesegments array (default: [])@type string (default: "GoogleDirectionsSegment")mode string nullable (one of: "driving", "bicycling", "walking", "transit")distance_meters integer nullableduration_seconds integer nullabledeparture_at integer nullablearrival_at integer nullabletransit_vehicle string nullabletransit_line string nullabletransit_headsign string nullabletransit_agency string nullabletransit_agency_phone string nullabletransit_agency_url string nullableservice_alerts array (default: [])@type string (default: "GoogleDirectionsServiceAlert")title string nullablesummary string nullabletext string nullableurl string nullablestart_at integer nullableend_at integer nullablesteps array (default: [])@type string (default: "GoogleDirectionsStep")instruction string nullablemaneuver string nullabledistance_meters integer nullableduration_seconds integer nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.