Saltar al contenido principal

Validate Your Test Order

Limited access

Marketplace APIs are not yet generally available. Please record interest in early access here.

Validating test orders is an essential step in confirming that your integration is working end-to-end. The Developer Portal provides Event Logs for visibility into what DoorDash sent to your webhook, while your own system logs help you confirm that orders were received, parsed, and processed correctly.

Validate in DoorDash Event Logs​

  1. Open Developer Portal → Event Logs.

  2. Filter

    • Time range: when you placed the test order
    • Event name(s): ORDER_CREATE, ORDER_UPDATE, ORDER_STATUS, ORDER_CANCELLED (auto-cancel ~90 min), and any POS callback events you expect
    • IDs: search by Order ID, External Store ID, or External Order ID (if you send one)

    Event Log Search

  3. Open the most recent entry and confirm:

    • HTTP status = 2xx from your endpoint
    • Retries = 0 (or that the final attempt succeeded)
    • Payload fields present: order_id, external_store_id, items[], totals, requested_time
    • Timestamps align with when you placed the order

Event Log Results

  1. Review payloads (if needed) and compare them to what your system received/processed.

Validate in Your System​

Inbound Webhook Receipt​

  • Confirm your logs show DoorDash requests hitting your webhook URL.
  • Match by order_id (DoorDash) and your external_order_id (if generated).

Schema & Parsing​

  • Verify all required fields parsed successfully (store mapping, item IDs/SKUs/modifiers, totals, taxes, fulfillment type).

Business Rules​

  • Ensure the order created in your POS/KDS matches: items, quantities, prices, notes, and pickup/delivery timing.

Acks/Responses​

  • Confirm you returned 2xx within your SLA.
  • Log the response body you sent back to DoorDash for traceability.

If Something Doesn't Look Right (Triage Before Escalation)​

No events in Event Logs​

  • Widen time range; check correct environment; search by external_store_id.
  • Re-place the order and note the exact timestamp.

Events show errors / retries​

Open the failing entry → note HTTP status and your system’s response body.

Common fixes:

  • 401/403 → check auth header/secret rotation
  • 404 → wrong path/env or store mapping
  • 422/400 → schema mismatch (missing required field, wrong type)
  • 5xx / timeout → increase webhook timeout, remove long DB calls, return 200 then process async

Order not in your POS/KDS​

  • Confirm your webhook handler actually creates the order after validating the payload.
  • Check ID mappings (store / item catalog) and reject rules.

Use Dev Chat AI in the Portal​

  • Paste the failing Event Log payload + your response body into the AI helper.
  • Follow step-by-step fixes suggested.

Re-test​

  • Place a fresh test order and repeat the checks in Event Logs and your system.
  • Keep one failing and one successful example captured for your records.

Escalate to DoorDash Support​

Only after you’ve completed the above steps should you escalate. Include:

  • Event Log IDs
  • Timestamps (UTC)
  • Your request/response samples
  • Test account email

Submit your issue through Support on the DoorDash Developer site.
Our team will review it and get back to you with next steps.