Skip to main content

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 after the build is complete, we require our integration partners to meet specific quality standards to guarantee a good customer experience. As part of this certification process all tests must be successfully completed and verified before certification is granted. If you have any questions on this, please reach out via the Dev Portal support form or directly to your Technical Account Manager (TAM).

Note: These quality standards are subject to change. Once updated, your team will have 6 months to make the required changes to meet the updated quality standards to continue onboarding additional stores in production.


  • Demonstrate Menu Creation using both Menu Pull and Menu Push methods that do not rely on menu scraping logic - Menu push methods are required to patch menu updates or send through new menus post-activation. - Menu pull methods are required to ensure our onboarding team has the ability to trigger menu creations during store setup.
  • Demonstrate a successful Menu Update by making a menu change
  • Real-time updates preferred; if real-time updates are not possible, explain the frequency + logic of the menu update process
  • Demonstrate removal of an Item and an Option from the Menu (permanent removal)
  • Demonstrate use of Store Hours and Store Special Hours
  • Demonstrate deactivation of a menu using the active flag
    • If a duplicate menu is sent or an incorrect menu is created, these should be deactivated using the active flag.
  • Demonstrate support for Dual Pricing (ability to send an inflated price and a non-inflated price)
    • The primary use case is to remove inflation for Pickup orders to protect our shared customer experience.
  • Demonstrate an Alcohol Flag to support marking items as alcoholic (not required if merchants are not selling alcoholic items)
    • In order for merchants to offer their alcohol items on DoorDash, they need to have the ability to indicate which items have age restrictions.
    • General steps and requirements for DoorDash merchants to sell alcohol found on this help page.
  • Support for sending image urls meeting our photo standards (see FAQ for more info)
    • This feature allows for seamless updates and additions of menu photos directly from the source.
    • Without integrated images, the merchant will have to manually upload photos within their Merchant Portal for each item.
      • Images then must go through an internal approval process.
      • If a new menu is ingested, the whole submission process will need to be completed once more.
  • Support for sending item nutritional information (calories + dietary tags)

Order Integration


  • Demonstrate successful confirmation of a new order (asynchronously or synchronously)
  • Demonstrate rejection of a new order with detailed failure reason information provided
  • Demonstrate use of Cancellation Webhooks from DD to Mx and Order Cxl webhooks from Mx to DD
    • To provide the best merchant experience, cancellation webhooks are required so the merchant has visibility into any orders that are canceled downstream. If a merchant is able to cancel orders on their end, this should also be demonstrated to confirm it is properly being received by DoorDash.
  • Support for consumption of Merchant Tip amount
    • Primary use case is for Pickup orders to allow user to leave a tip for the restaurant staff
  • Support for consumption of the Experience indicator
    • Primary use case is for reporting/reconciliation to understand the origin of where the order placed - DoorDash, Caviar, Storefront.
  • Demonstrate use of the Order Ready Signal
    • Allow the merchant to update an order’s ready for pick up status, ensuring the fastest and freshest delivery possible by reducing dasher wait.
  • Demonstrate consumption of Dasher Status Notifications
    • To provide visibility for merchants into where their dasher is throughout the order pick up process to reduce dasher wait.
  • Demonstrate accurate usage of prep times if being passed
    • If not provided, DoorDash calculated prep times will be used

Store & Menu availability


  • Demonstrate real time store deactivation/activation using webhooks for both lost POS Connectivity + Operator manually disabling online ordering
    • This is critical to support in-store merchant operations and the customer experience when a merchant is unable to receive orders
  • Real time Item + Option deactivation/activation using webhooks for 86’ing
    • This is critical to support in-store merchant operations when an item becomes unavailable and to prevent downstream cancellations should a customer order an item that is actually not available.

Onboarding Requirements

Please defer to Onboarding Requirements to ensure your integration meets the proper onboarding standard.

Enablement Requirements

If you are a third-party integration partner, you will also be required to share merchant facing enablement materials during certification in order to be granted production access. This includes:

  • A link to your Merchant facing portal i.e where a Merchant can log in to begin the onboarding process and/or manage their integration.
  • A URL for a help article where Merchants can find information on menu and store availability management to educate Merchants on how to manage their menus, 86 items, and configure store hours.
  • A URL for a help article where merchants can find any other key additional information on managing their stores once integrated i.e how to pause their store, manage orders, etc.