DoorDash Address Geocoder: Address to GPS & ZIP

Paste a list of US street addresses and get back, for each one, up to three matches from DoorDash's own address lookup: a normalised address, street, city, state, ZIP, latitude, longitude and country. No login, no API key.

It is a lightweight batch geocoder and address normaliser, handy for cleaning address lists, adding coordinates to a spreadsheet, or checking that an address exists before using it elsewhere.

What you get

Field	Description
query	The text you searched for
matchRank	1 = best match, then 2 and 3
name	Short label DoorDash shows (the street line or a business name)
address	Full normalised address, e.g. 350 5th Ave, New York, NY 10118, USA
street, unit, city, state, postalCode	Parts of a US address (best-effort split, empty for non-US)
latitude, longitude	Coordinates of the match
country	ISO country code
place_id	DoorDash's opaque address token for the match. Not a Google Maps Place ID: it changes on every request, so do not store it as an identifier. Use address or the coordinates instead.

Use cases

• Add latitude/longitude and ZIP codes to a list of delivery or customer addresses.
• Normalise messy address text (350 5th ave nyc) into one consistent format.
• Check which of several candidate addresses DoorDash recognises.

Input

Parameter	Type	Description
queries	array	One address per line (required). Include the city and state.
maxMatchesPerQuery	integer	Keep the top N matches per address, 1 to 3 (default 3).
proxyConfiguration	object	Optional proxy. Leave empty for a direct connection.

The older single-address input ({"q": "New York"}) is still accepted. A radius value is ignored: DoorDash's lookup has no effect from it.

{
    "queries": [
        "350 5th Ave, New York, NY",
        "1600 Amphitheatre Parkway, Mountain View, CA"
    ],
    "maxMatchesPerQuery": 3
}

Example output

{
    "query": "233 S Wacker Dr, Chicago, IL",
    "matchRank": 1,
    "name": "233 S Wacker Dr",
    "address": "233 S Wacker Dr, Chicago, IL 60606, USA",
    "street": "233 S Wacker Dr",
    "unit": null,
    "city": "Chicago",
    "state": "IL",
    "postalCode": "60606",
    "latitude": 41.87878796830773,
    "longitude": -87.63649600557983,
    "country": "US",
    "place_id": "AbQ8T-7jVOPMTu..."
}

Good to know

• US-focused. DoorDash serves the US, Canada, Australia and a few other markets, and its lookup favours the area of the server's own location. Ambiguous or very short text can return addresses far from the one you meant, so include city and state. A query with no match (for example a street in London) simply returns no row.
• At most 3 matches per query. DoorDash caps the list. This is a geocoder, not a bulk place export.
• Fuzzy matching. DoorDash may return the nearest street number it knows, so check address against what you asked for.
• Looking for places and businesses near a point? Use the companion actor "DoorDash Address & Place Autocomplete" (doordash-store-scraper), which biases suggestions to coordinates you give. This actor is for batch address-to-coordinates lookups.

Scheduling and integrations

Run it on a schedule, trigger it from a webhook, or call it from the Apify API, Zapier, Make or n8n. Results are available as JSON, CSV or Excel from the dataset.

FAQ

Is the place_id a Google Place ID? No. It is a DoorDash-issued token and is different every time you ask, even for the same address.

Does it need a DoorDash account? No. It uses an anonymous guest session created at the start of each run.

Why does a query return nothing? DoorDash found no match. Try adding the city and state, or check that the address is in a market DoorDash serves.