Skip to main content
POST
Creates a delivery order, then automatically attempts to dispatch it to the nearest eligible driver. See Authentication for how to get a key, and Order Lifecycle for what happens after this call.

Headers

string
required
Bearer rk_your_api_key — see Authentication.
string
required
application/json

Body

string
required
Your store’s Rushly ID, given to you alongside your API key.
object
required
string
required
Your store’s address, as a single formatted string (e.g. "123 Fashion Ave, Irvine, CA 92614").
object
required
string
default:"standard"
One of standard, priority, or scheduled. See Delivery Tiers for pricing and what each means for dispatch.

Response

string
The order’s ID. Not needed for anything client-facing — use tracking_token for that — but useful for your own records.
string
pending_dispatch if no driver was immediately available, driver_assigned if dispatch succeeded synchronously. See Order Lifecycle for the full set of values and how status changes after this point.
string
Echoes back the tier that was used (defaults to standard if you didn’t send one).
integer
The price charged for this delivery, in cents. Always derived server-side from delivery_tier — see Delivery Tiers.
string
Whether your store’s card on file was successfully charged. See Order Lifecycle.
string
The token in the customer’s tracking link: https://rushly.us/track/{tracking_token}.
A few other fields are present on order (customer_id, driver_id, dropoff_address_id, stripe_charge_id, timestamps, and some driver-payout bookkeeping fields) — they’re internal and safe to ignore.

Errors

object
delivery_tier was set to something other than standard, priority, or scheduled.
object
The API key is missing or wrong, doesn’t match the retailer_id you sent, or your store’s status isn’t active yet. Double-check both values are exactly what you were given — see Authentication.
object
Something went wrong on Rushly’s end. Safe to retry; contact support@rushly.us if it persists.