Connect DoorDash to ECA
Give ECA governed access to DoorDash’s 32 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add DoorDash to ECA in four steps
Admins approve the server once. Everyone in ECA then gets it through the same governed connection.
- 1
Approve DoorDash in Runlayer
Add DoorDash from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect ECA to Runlayer
Users add the Runlayer Plugin to ECA by following Runlayer’s setup guide. ECA reaches DoorDash’s 32 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
ECA setup guide - 3
Sign in to DoorDash
Each user signs in to DoorDash with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use DoorDash from ECA
DoorDash’s approved tools appear in ECA. Every call is checked against policy and recorded.
Tools
32 DoorDash tools in ECA
Runlayer policy decides which of these ECA users can call. 10 read data only.
Get meal manager calendars
List the corporate Meal Manager (DoorDash for Work) calendars the authenticated consumer has access to, and the dated group carts on each one.
Add to cart
Add items from a restaurant's menu to the consumer's cart, creating or updating the cart.
List delivery addresses
Get all saved delivery addresses for the authenticated consumer.
Set delivery address
Set the default delivery address for the authenticated consumer.
Find address
First step of adding a NEW delivery address: resolve a free-text street address into concrete candidates for the user to confirm.
Save address
Second step of adding a NEW delivery address: save the address the user confirmed (by place_id from a prior find_address result).
Get cart
Retrieve the consumer's cart.
Remove cart item
Remove a specific item from the consumer's cart.
Control
What Runlayer can see and stop in ECA
Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.
Gateway policy (available)
Every DoorDash call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.
Frequently asked questions
Connect more