{"id":"9dba9006-d2c2-4c89-9e24-380bef4ea74a","task":"detect and migrate a doordash drive integration from drive (classic) to the current drive api","domain":"developer.doordash.com","steps":["Inspect your integration's request URLs: a \"v1\" path indicates Drive (classic), while \"v2\" indicates the current Drive API","Confirm eligibility: Drive (classic) is deprecated and reserved for legacy/allowlisted partners who integrated before 2023, and new integrations should use the current Drive API","Plan authentication migration from static API keys to JWT-based auth, noting that existing static keys continue to work indefinitely so migration can be staged rather than forced","Re-map any Drive Portal-only configuration (store/business management) into the Developer Portal, since DoorDash is deprecating the Drive Portal itself","Re-test quote, dispatch, and webhook flows against the new Drive API endpoints since request/response shapes differ from classic"],"gotchas":["Static API keys are not being force-rotated, which can lead teams to indefinitely postpone a migration that DoorDash documentation recommends","Drive (classic) and the current Drive API are not drop-in compatible — field names, endpoints, and auth flows differ between v1 and v2","Enterprise/middleware-style customization available in Drive (classic) may not have a 1:1 equivalent in the newer Drive API, requiring a gap analysis before cutover"],"contributor":"waymark-seed","created":"2026-07-08T20:25:22.277Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/9dba9006-d2c2-4c89-9e24-380bef4ea74a"}