Update your Legacy Marketplace Integration
Overview
DoorDash has built the Developer Portal to enable Integration Partners to have a more hands-on experience where they can view/manage their Marketplace and Drive integrations from one central place.
Partners who were onboarded via the legacy Marketplace integration need to update their integration to meet our Developer Portal requirements to ensure the integration will continue to be supported.
Required Updates Partners must complete
- Gain access to Developer Portal by following the appropriate Migration Process
- Update integration hostname to https://openapi.doordash.com/marketplace
- Update URL Paths to the updated versions outlined below
- Update to our new JWT authentication method outlined here
Migration Process
The migration process is different for Partners who only have a DoorDash Marketplace integration versus Partners who have both DoorDash Marketplace AND DoorDash Drive integrations.
To ensure your Migration to the Developer Portal goes smoothly, please follow the proper process that applies to you below:
- Marketplace ONLY Partners: Follow this process
- Marketplace AND Drive Partners: Follow this process
Migration FAQs
How do I know if our integration is a Legacy integration that needs to be updated?
If you are using the Hostname https://pointofsale.doordash.com, for your integration, you have a legacy integration that needs to be updated.
Can we make the required updates in phases?
Some examples are:
- Changing the Hostname and URL Paths but not using to JWT Auth yet
- Updating an x amount of your Hostname and URL Paths one week and the other x amount another time
- Updating to JWT Auth, but not updating the HostName or URL paths yet
Partners are able to make these changes in stages but MUST ensure that the HostName and URL paths are updated together.
For example, if a Partner updates their HostName for their Activation Status endpoint, they must also ensure that the URL path for this call is also updated. If they mix the legacy hostname with the new URL paths, the calls will fail.
Correct: https://openapi.doordash.com/marketplace/api/v1/stores/{location_id}/status
Incorrect: https://pointofsale.doordash.com/marketplace/api/v1/stores/{location_id}/status
How do I know if I have fully updated my integration?
When you have 100% successfully updated your integration, a Technical Account Manager will reach out to you and let you know that you have successfully updated all items including the Hostname, URL paths and JWT.
Are changes required for the bearer token that is sent with the webhooks from DoorDash to the Partner environment?
No, no changes are required. The changes needed here are strictly for calls to the Doordash API.
What should I do if I submitted a support request to share my email, and I have not heard back?
If you have submitted the email you used to kick off the migration process and have not heard anything, please reach out to your Technical Account Manager.
If you are not sure who your Technical Account Manager is, please submit another ticket by filling out this form and using the ID 2305617399 for the field “DoorDash Store ID”.
What happens if I do not migrate before the deadline?
Your integration will be at risk of losing core functionality and you will be unable to enjoy the benefits of our new Developer Portal. If you have any questions or concerns with the deadline, please work with your Technical Account Manager.
Updated URL Paths for Migration
The legacy integration used different URL Paths that will need to be updated to fully migrate your legacy integration to Developer Portal.
Order Endpoint Updates
These URL Paths for Order Endpoints will need to be updated to the Updated Order Endpoints in the 2nd Column of the below table. Please make sure to update these URL paths in staging/sandbox and production environments.
| Legacy Order Endpoints | Updated Order Endpoints |
|---|---|
| /api/v1/orders/{id} | /api/v1/orders/{id} |
| /v1/external/orders | /api/v1/external_orders |
Menu Endpoint Updates
These URL Paths for Menu Endpoints will need to be updated to the Updated Menu Endpoints in the 2nd Column of the below table. Please make sure to update these URL paths in staging/sandbox and production environments.
| Legacy Menu Endpoints | Updated Menu Endpoints |
|---|---|
| /api/v1/menus | /api/v1/menus |
| /api/v1/menus/{menu_id} | /api/v1/menus/{menu_id} |
Store Endpoint Updates
These URL Paths for Store Endpoints will need to be updated to the Updated Store Endpoints in the 2nd Column of the below table. Please make sure to update these URL paths in staging/sandbox and production environments.
| Legacy Store Endpoints | Updated Store Endpoints |
|---|---|
| /api/v1/stores/{merchant_supplied_id}/activation-status | /api/v1/stores/{merchant_supplied_id}/status |
| /api/v1/stores/{merchant_supplied_id}/item/activation-status | /api/v1/stores/{merchant_supplied_id}/items/status |
| /api/v1/stores/{merchant_supplied_id}/items | /api/v1/stores/{merchant_supplied_id}/items |
| /api/v1/stores/{merchant_supplied_id}/item_option/activation-status | /api/v1/stores/{merchant_supplied_id}/item_options/status |
| /api/v1/stores/{merchant_supplied_id}/menu_details | /api/v1/stores/{merchant_supplied_id}/menu_details |
| /api/v1/stores/search | /api/v1/stores/search |
| /api/v1/stores/{merchant_supplied_id} | /api/v1/stores/{merchant_supplied_id}/store_details |