D

doordash.com

DoorDash provides food ordering, local commerce, and on-demand delivery services. Its developer platform supports merchant, delivery, advertising, and reporting integrations for businesses and partners.

8 integrations · MCP · REST

DoorDash exposes multiple HTTP APIs (Drive, Drive classic, Marketplace, Marketplace legacy, Marketplace for Retailers, Ads, and Reporting) plus an OAuth-protected MCP server at https://openapi.doordash.com/mcp/consumer.

discovered 1d ago
MCP servers1
REST · OpenAPI7
Credentials
DoorDash developer credential set (developer ID, key ID, signing secret) used to mint JWT bearer tokenscompoundGet key ↗

In the DoorDash Developer Portal, open Credentials, click Create Credential (or create an access key in the Drive tutorial), choose the environment/APIs, and save the returned developer_id, key_id, and signing_secret/access key details. DoorDash docs say these values are then used to generate a JWT for API calls; the signing secret is shown only once, so store it securely. See Drive JWT auth, Drive get started, and Marketplace JWT auth.

DoorDash Ads API keyapi_keyGet key ↗

Use the DoorDash Developer Portal to obtain an Ads API key for Ads integrations. The Ads API reference names the auth scheme Ads API Key Authentication, but the docs page scraped here does not expose the exact issuance steps or header name, so confirm the binding in the Ads reference/portal for your account.

DoorDash Marketplace (legacy) access tokenbearer

Marketplace (legacy) requests use an authorization header with format [type] [credentials] plus a user_agent header. The public docs do not describe a self-serve token creation flow on the scraped pages, so obtain this legacy access token through DoorDash onboarding/support for existing Marketplace (legacy) integrations. See the Marketplace (legacy) API reference.

conventions · 0/7 published

Publish these signals → /publishing