Aller au contenu principal

General Integration Requirements

Limited access

Marketplace APIs are not yet generally available. Please record interest in early access here.

In order to gain access to production, integration partners must complete a certification process to guarantee a high-quality merchant experience. Certification requires successful demonstration of every required feature. All tests will be verified by DoorDash prior to granting production access.

Unless otherwise specified when sandbox access is granted, partners are expected to submit screen recordings of each required feature for asynchronous certification. Questions about requirements and certification can be directed to the Developer Portal support form.

Required Features and Validations​

  • ☐ Demonstrate Menu Creation – POST a menu, confirm success in DoorDash preview and event logs
  • ☐ Demonstrate Menu Update – PATCH a menu item, confirm success in DoorDash preview and event logs
  • ☐ Demonstrate Menu Status Webhook – Trigger a failed POST, display failure to merchant, confirm webhook details
  • ☐ Support real-time menu updates – At least one update per store per day
  • ☐ Demonstrate Item/Option Deactivation & Reactivation – Remove and re-add, confirm in DoorDash preview and event logs
  • ☐ Demonstrate Menu Deactivation & Reactivation – Set active:false, confirm deactivation, then active:true, confirm reactivation
  • ☐ Demonstrate Menu Pull – Use Developer Portal ingest tool, confirm success in preview and logs
  • ☐ Demonstrate Menu Update via Pull – Use update tool, confirm success in preview and logs
  • ☐ Validate Store Open Hours – Add regular hours in partner environment, confirm in DoorDash
  • ☐ Validate Store Special Hours – Add closure (e.g., tomorrow), confirm in DoorDash
  • ☐ Validate Integrated Images – Add image URL, confirm image appears in DoorDash and payload
  • ☐ Validate Alcohol Flag – Mark item alcoholic, confirm restricted ordering and payload flag = true
  • ☐ Validate Dual Pricing – Configure delivery vs. pickup prices, confirm correct display in DoorDash and payload
  • ☐ Support nutritional information (calories + dietary tags)

Availability Requirements​

Required Features and Validations​

  • ☐ Demonstrate Item 86'ing – Deactivate/reactivate item, confirm activation webhook in logs and DoorDash preview
  • ☐ Demonstrate Item Option 86'ing – Deactivate/reactivate modifier option, confirm webhook and DoorDash preview
  • ☐ Demonstrate Store Availability – Deactivate/reactivate store using activation status endpoint, confirm in logs and DoorDash preview

Order Requirements​

Required Features and Validations​

  • ☐ Place and Confirm Incoming Order – Place test order, confirm in partner environment and logs
  • ☐ Reject New Order – Fail order intentionally, confirm error surfaced in DoorDash and failure reason logged
  • ☐ Validate Merchant Tips – Place pickup order with tip, confirm value ingested in partner environment
  • ☐ Order Cancellation (DoorDash → Merchant) – Cancel order in DoorDash, confirm webhook receipt and logs
  • ☐ Order Cancellation (Merchant → DoorDash) – Cancel order in partner environment, confirm cancellation in DoorDash and logs
  • ☐ Order Ready Signal – Mark order ready, confirm signal received in logs
  • ☐ Validate Experience Flag – Confirm ingestion and display of order origin (Storefront, Caviar, DoorDash)
  • ☐ Demonstrate consumption of Dasher Status Notifications

Onboarding Requirements​

Partners must build the onboarding flow appropriate to their integration type:

  • Self-Serve Integration Onboarding (SSIO): Required for middleware platforms serving multiple merchants.
  • Store Onboarding Webhook (SOW): Required for single-merchant integrations.

SSIO – Existing DoorDash Merchants​

  • ☐ Kick-off option visible ("Add DoorDash Integration")
  • ☐ Clear messaging that activating will break existing integrations
  • ☐ OAuth into DoorDash successfully
  • ☐ Fetch DoorDash stores as Business Admin, display eligible and ineligible stores (grayed out)
  • ☐ Display Partner Store Name + DoorDash Store Name together
  • ☐ Menu Pull automatically after store selection → confirm menu_qualified status
  • ☐ Activate store → confirm integration_activated status

SSIO – Net New DoorDash Merchants​

  • ☐ Display option: "New to DoorDash? Sign up here"
  • ☐ Redirect to deep link sign-up URL with prefilled fields
  • ☐ Show store activation upon completion of SSIO

SSIO – Exclusion Scenarios​

  • ☐ OAuth with non-business admin → display error and re-auth instructions
  • ☐ Demonstrate MENU_BLOCK status (e.g., missing hours) → resolve via re-ingestion
  • ☐ Menu update resolves block → status moves to menu_qualified
  • ☐ Net new flow triggered when no stores are returned

SOW – Single Merchant​

  • ☐ Send onboarding webhook with correct location_id and address fields
  • ☐ Confirm webhook logged in Developer Portal
  • ☐ Pull menu for test store, confirm success in logs and preview
  • ☐ Confirm webhook contents are programmatically sourced from merchant data

Onboarding SLA Requirements​

  • ☐ 14-Day Partner SLA – Complete partner-side onboarding steps within 14 days of request, followed immediately by webhook to DoorDash
  • ☐ 48-Hour Escalation SLA – Resolve visible menu issues within 48 business hours of webhook timestamp

Failure to meet SLA requirements may result in suspension of all new onboarding requests.

Operational Requirements​

  • ☐ Support Virtual Brands – Unique location_id per virtual concept
  • ☐ Support Multi-location Onboarding – Native support, or confirm CSV upload via Developer Portal
  • ☐ Support Change of Ownership / Restart – Allow merchant to re-run SSIO for a new binding
  • ☐ Listen for all onboarding status webhooks in production
  • ☐ Configure production webhook subscription in Developer Portal
  • ☐ Allowlist all production redirect URLs
  • ☐ Support spec versioning (account for changes and enhancements)
  • ☐ Share partner environment URL for merchant onboarding

General Requirements​

  • ☐ Accept new fields and field values without rejecting orders (e.g., new webhook fields, int → bigint)

Failure Reason Documentation​

  • ☐ Provide failure message strings and meanings
  • ☐ Document responsible DRI per failure
  • ☐ Provide troubleshooting steps (merchant vs. technical team)
  • ☐ Link to relevant help articles
  • ☐ Include supporting data (timestamps, store IDs, etc.)

Merchant-Facing Materials​

  • ☐ Link to merchant-facing portal
  • ☐ Provide help article for menu & availability management (menus, 86'ing, store hours)
  • ☐ Provide help article for store operations (pause store, manage orders, etc.)

Quality Requirements​

  • ☐ Maintain order failure rate below 1%
  • ☐ Maintain merchant cancel rate below 1%

Failure to maintain quality standards may result in removal from DPIP webpage, suspension of onboarding, or revoked API access. Updated requirements will allow 6 months for compliance before enforcement.