Order Lifecycle

Statuses

An order’s status field moves through these values:

Status	Meaning
`pending_dispatch`	Order created, no driver assigned yet. This is the starting state, and where an order stays queued if no eligible driver was available at creation time.
`driver_assigned`	A driver has accepted the delivery.
`arrived_at_pickup`	Driver has arrived at your store.
`picked_up`	Driver has the order and is heading to the customer.
`delivered`	Delivered, with a proof-of-delivery photo on file.
`failed`	Delivery could not be completed.

There’s no polling endpoint for order status today — the reliable way to follow an order is the customer-facing tracking link (below), which updates live. A dedicated status endpoint / webhook for your own backend is on the roadmap; reach out at support@rushly.us if that’s a blocker for your integration.

Tracking

Every order gets a tracking_token in the create-order response. The customer’s confirmation text links to:

https://rushly.us/track/{tracking_token}

That page shows live status and, once a driver is en route, their live location — no login required, and it’s the same link your customer already received by SMS.

Billing

Each order also has a payment_status, reflecting whether your store’s card on file was successfully charged for that delivery:

`payment_status`	Meaning
`pending`	Not charged yet — order hasn’t been dispatched to a driver, or the charge is still processing.
`succeeded`	Charged successfully.
`failed`	The charge was attempted and declined.
`no_payment_method`	Your store has no card on file yet.

A billing issue never blocks or delays dispatch — an order can be fully delivered while payment_status is still failed or no_payment_method. If you see either of those, get in touch so we can get your card on file sorted out.

Get Started

Concepts

API Reference

Order Lifecycle

Statuses

Tracking

Billing

​Statuses

​Tracking

​Billing

Statuses

Tracking

Billing