Skip to main content
GET
Read where an order is

Merchants that report a delivery stage

  • DoorDash
An order at a DoorDash store answers with its live stage, such as picked_up or arriving, while tracking is live. An order at any other merchant answers placed, confirmed or canceled from what the merchant told checkout, with tracking: not_available.

Authorizations

Authorization
string
header
required

The user's connection access_token (user authentication), or an org-minted buy_token for org-owned accounts.

Path Parameters

order_id
string
required

The order_id from order.placed, or from an order in GET /buy/conversations/{id}.

Query Parameters

user_id
string

The connected person whose order this is. Required with a platform access token: a read that leaves it out is refused with 400 user_id_required. Leave it out with a user token, which names the person itself.

Response

The order.

order_id
string
merchant
string
merchant_name
string
conversation_id
string | null
status
enum<string>

The delivery stage, in Agentcard's words for every merchant.

Available options:
placed,
confirmed,
courier_assigned,
courier_at_store,
ready_for_pickup,
picked_up,
arriving,
delivered,
canceled
status_updated_at
string<date-time> | null

When the order reached this stage.

estimated_arrival
object | null

The arrival window the merchant quotes, or null when it quotes none.

tracking
enum<string>

live while Agentcard follows the order, ended once it stopped (delivered, canceled, past six hours, or gone from the merchant more than two hours after it was placed), not_available for a merchant it cannot follow.

Available options:
live,
ended,
not_available
checked_at
string<date-time> | null

When Agentcard last tried to read the order from the merchant. A try that read nothing moves this time too, so read status_updated_at for how old the stage itself is.

placed_at
string<date-time> | null