@kody/doordash-driverFork

@kody/doordash-driver

Intent

Reusable DoorDash Drive helpers so Kody agents can request Dasher deliveries (quotes + create/get delivery) on the caller's Drive access key — not consumer food ordering on doordash.com, and not a shared platform connection. Auth is a Developer Portal access key: developer_id and key_id in package settings, plus a saved signing_secret. Mutations default to a dry-run preview and need confirm: true to run live.

For ordering food as a DoorDash customer, use @kody/doordash instead.

This listing is meant to be forked. After you fork, call ./adapt, save your own Portal fields, and publish your copy.

Share this package as https://kody.codes/@kody/doordash-driver

What it does

• Mint Drive JWTs (HS256, dd-ver: DD-JWT-V1) for openapi.doordash.com
• Create delivery quotes and accept them
• Create and read deliveries
• Fork playbook via ./adapt and owner knobs via ./settings

Prerequisites / setup

1. Create an access key at developer.doordash.com/portal/auth/credentials. Prefer a sandbox key first. Never paste the signing_secret into chat.
2. Save Portal UUIDs in this package's storage:

import settings from 'kody:@kody/doordash-driver/settings'
await settings({
  developerId: '…', // developer_id from the access key JSON
  keyId: '…',       // key_id from the access key JSON
})

3. Save the signing secret:

https://kody.codes/account/secrets/new?name=doorDashSigningSecret&description=DoorDash%20Drive%20signing_secret%20(base64)%20from%20developer.doordash.com%20Portal%20access%20key%20JSON&allowedHosts=openapi.doordash.com&scope=user

4. In the account secrets UI, approve host openapi.doordash.com on that secret. Saving a secret does not approve hosts by itself.
5. Agents: see AGENTS.md for import paths and smoke checks.

Sandbox and production share openapi.doordash.com. The access key environment in the Portal decides which fleet you hit.

Additional accounts

Pass account: "work" to use doorDashSigningSecret-work, or pass signingSecretSecret explicitly. Keep separate developer/key ids in settings on forked copies when you need multiple apps.

Adapt this fork

After community_fork, import ./adapt and follow its steps. Put owner-specific Portal ids in ./settings (package storage) so the official @kody listing does not change.

License

MIT