Connect DoorDash Drive: quote, dispatch and track local deliveries

Copy Developer ID, Key ID and Signing Secret from the Credentials page of the DoorDash Developer Portal, set one pickup option in Integration — a pickup address, or an External Business ID plus External Store ID pair — test, and start requesting DoorDash Drive deliveries.

The DoorDash connector requests DoorDash Drive local deliveries from this system: it gets a quote, creates a delivery, checks delivery status, and can cancel a delivery. It is a last-mile delivery connection only — it does not pull DoorDash marketplace orders into this system, and it does not sync menus or store catalogs. Quotes and deliveries run under your own DoorDash Drive account and pickup location.

Prerequisites#

• A DoorDash Drive account, and access to the DoorDash Developer Portal, where the Credentials page shows your Developer ID, Key ID and Signing Secret.
• You know how pickups should be identified: either the single-line pickup address of your store or warehouse, or a store already registered with DoorDash that you can name with its External Business ID and External Store ID. The address and the ID pair are alternatives — decide which one you will use before you start.
• The pickup business name and a phone number a dasher can call at pickup, if you want them shown for the pickup — for example the store name and its direct line.

Get your credentials#

1. Sign in to the DoorDash Developer Portal and open the Credentials page.
2. Copy the Developer ID shown on that page. It identifies your developer account and is one of the three values the connection signs requests with.
3. Copy the Key ID shown on the same Credentials page.
4. Copy the Signing Secret shown on the same Credentials page, in full. The Key ID and the Signing Secret belong together as a pair, and the Signing Secret is a base64 value the connection uses to sign a short-lived token for each request — copy it from the same page as the Key ID, not from another key pair.

Fill it into Integration#

1. Open Integration → Connector Marketplace → DoorDash → New connection.
2. developer_id — required, Developer ID: paste the Developer ID from the DoorDash Developer Portal → Credentials page.
3. key_id — required, Key ID: paste the Key ID from the same Credentials page.
4. signing_secret — required, Signing Secret: paste the Signing Secret from the same Credentials page, in full. It is a password-type field and is stored as a secret.
5. Now pick ONE pickup option — Option A, the address: fill pickup_address with the single-line pickup address of your store or warehouse, for example 901 Market Street, San Francisco, CA 94103, US, and leave the two External ID fields empty.
6. Option B, a registered store: leave pickup_address empty and fill BOTH pickup_external_business_id (External Business ID) and pickup_external_store_id (External Store ID) with the IDs of the store registered with DoorDash. The two IDs must always be filled together as a pair — filling only one of them does not work, because a registered store address only takes over the pickup address when both IDs are present.
7. pickup_business_name — optional, Pickup business name: the name shown to the dasher for the pickup, for example your store name. pickup_phone_number — optional, Pickup phone number: a number the dasher can call at pickup, for example +16505550100.
8. user_agent — optional, User-Agent: in most cases leave it empty; the connection then uses its default value, Docklify/1.0.

Test the connection#

Click Test connection. The test first checks that all three credential values are present — developer_id, key_id and signing_secret — and stops without sending a request if any of them is missing. With all three present, it signs a short-lived token (five minutes) from the three values and uses it to look up a delivery that does not exist: docklify-probe-nonexistent. DoorDash answering 404 is the pass: it means the signed token was accepted and only the made-up delivery is missing, so the expected result of this test is a 404, not an error to fix. A 401 or 403 answer is reported as AUTH_FAILED and is the real failure: DoorDash rejected the signed token. If you run the test before saving any credentials, the result is a simulation check only — save the real credentials and test again for a real result. The test does not create a delivery and does not check your pickup address or your External ID pair, so a wrong pickup setting can still pass the test and only fail later, at quote or delivery time.

Mapping / pick a template#

DoorDash Drive needs no order mapping — it works on deliveries, not orders. What you confirm here is the pickup setup from the fill-in step, plus the delivery fields each request carries: pickup comes from either your pickup_address or your registered store (External Business ID plus External Store ID), and each delivery request uses the drop-off address, contact and items from the shipment in this system. Before activating, create one real quote and one test delivery to your own address and check the pickup name, pickup phone and drop-off details side by side with the shipment.

Activate#

After activation, shipments in this system can request DoorDash Drive deliveries: the connection quotes the delivery, creates it after the quote is accepted, keeps the delivery status on the shipment, and can cancel a delivery that has not been picked up yet. Watch the first real deliveries in Runs / Logs and compare the pickup and drop-off details with DoorDash before leaving the connection unattended.

What this connection does not do: it does not bring DoorDash marketplace orders into this system, it does not sync menus or store catalogs, and it does not settle dasher pay or DoorDash billing for you. It only quotes, creates, tracks and cancels DoorDash Drive deliveries for shipments you send through it.

FAQ#

The test mentions 404 — did it fail?

No — for DoorDash Drive, that 404 is the success signal. The test deliberately looks up a delivery that does not exist, docklify-probe-nonexistent. Getting a not found answer means DoorDash accepted the token signed from your developer_id, key_id and signing_secret, and only rejected the made-up delivery.

Treat the test as passed and continue to activation. Only a 401 or 403 answer, reported as AUTH_FAILED, means the test really failed.

Test fails with AUTH_FAILED, 401 or 403

DoorDash rejected the signed token, which means one of the three values does not match: developer_id, key_id or signing_secret was copied wrong, or the Signing Secret you pasted does not belong to the Key ID you pasted — the two are a pair issued together on the Credentials page.

Go back to DoorDash Developer Portal → Credentials page and re-copy all three values from that same page: Developer ID into developer_id, Key ID into key_id, and the Signing Secret that belongs to that Key ID into signing_secret, in full. Then test again.

Test stops before sending anything because a credential is missing

The test signs its token from all three credential values, so it cannot even start when one is missing: without developer_id, key_id and signing_secret together, there is nothing to sign with, and the test stops instead of sending a request that cannot succeed.

Fill in all three fields from the DoorDash Developer Portal → Credentials page, save the connection, and test again. Only test without credentials if you just want the simulation check — save the real values for a real result.

I filled only one of the two External ID fields and pickups do not work

The External Business ID and the External Store ID only work as a pair. A registered store address takes over the pickup address only when both IDs are present together — with just one ID, the connection has neither a complete registered store nor, if you left the address empty, a pickup address at all.

Pick one option and complete it: either fill BOTH pickup_external_business_id and pickup_external_store_id for the registered store, or clear both ID fields and fill pickup_address with the single-line pickup address instead. Then quote again.

Test passes, but creating a delivery fails on the pickup side

The connection test only proves the credentials: it signs a token and probes a delivery that does not exist. It does not check your pickup address or your External ID pair, so a missing address, an incomplete ID pair, or an ID pair for a store that is not registered can pass the test and only surface when a real quote or delivery tries to use that pickup.

Check the pickup option on the connection: pickup_address filled as a complete single-line address, or both External ID fields filled for a store registered with DoorDash — not a mix, and not a single ID. Fix it, save, and run the quote again before creating the delivery.

The dasher goes to the wrong place or cannot reach anyone at pickup

The dasher follows what the connection sends for the pickup: the pickup address (or the registered store behind your External ID pair), the pickup_business_name shown for the pickup, and the pickup_phone_number the dasher can call. If any of those is wrong or missing, the dasher gets the wrong place, the wrong name, or no working number.

Correct the pickup fields on the connection: the pickup address or the registered-store ID pair, pickup_business_name as the name staff at the pickup will recognise, and pickup_phone_number as a number that is answered at pickup time. Save and use the corrected values for the next delivery — deliveries already created keep the pickup details they were created with.