Plug courier delivery
into your ordering.

Ways to integrate

Three ways in, depending on who you are. All three end the same way: the cheapest quote is booked and the guest tracks the courier.

API v1 draft

Overview

• Base URL (draft): https://deliveree.online/api/v1
• JSON request and response bodies; send Content-Type: application/json.
• Money is an integer number of cents (value_cents, fee_cents, tip_cents).
• Times are ISO 8601 in UTC, e.g. 2026-09-22T18:30:00Z.
• ETAs come from the courier networks and are estimates, not promises.
• Values in the examples are made up. They are not prices.

The flow is always the same: quote a trip, book one of the options, then follow it by webhook (or poll it).

Authentication

Every request carries a secret key in the Authorization header:

Authorization: Bearer dlv_live_…

• Live keys start dlv_live_. Test keys start dlv_test_: use them while you build. No courier is sent and nothing is billed on a test key.
• One key per merchant (per restaurant). A request made with a merchant key acts for that merchant only.
• Agencies get a partner key that can act for each of their merchants. How a request names the merchant it is for is not settled in this draft.
• Keys are secrets. Keep them on your server, never in a browser or an app bundle.

Get quotes

POST/api/v1/quotes

Ask the courier networks what a trip would cost. The response lists every option that came back and names the cheapest.

curl https://deliveree.online/api/v1/quotes \
  -H "Authorization: Bearer $DELIVEREE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "pickup": {
      "name": "Luna Pizza",
      "address": "120 Main St, Tampa, FL 33602",
      "phone": "+18135550142",
      "ready_at": "2026-09-22T18:30:00Z"
    },
    "dropoff": {
      "name": "Sam Rivera",
      "address": "845 Bayshore Blvd, Apt 4B, Tampa, FL 33606",
      "phone": "+18135550199",
      "notes": "Buzz 4B"
    },
    "order": {
      "value_cents": 4250,
      "items": [
        { "name": "Large Margherita", "quantity": 1 },
        { "name": "Garlic Knots", "quantity": 2 }
      ]
    },
    "tip_cents": 500
  }'

{
  "quote_id": "qt_8Hc2kPz4",
  "expires_at": "2026-09-22T18:10:00Z",
  "options": [
    {
      "network": "doordash",
      "fee_cents": 1000,
      "pickup_eta": "2026-09-22T18:31:00Z",
      "dropoff_eta": "2026-09-22T18:52:00Z"
    },
    {
      "network": "uber",
      "fee_cents": 1100,
      "pickup_eta": "2026-09-22T18:34:00Z",
      "dropoff_eta": "2026-09-22T18:50:00Z"
    }
  ],
  "cheapest": "doordash"
}

Book a delivery

POST/api/v1/deliveries

Book one of the options from a quote. Deliveree picks the option by strategy.

curl https://deliveree.online/api/v1/deliveries \
  -H "Authorization: Bearer $DELIVEREE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "quote_id": "qt_8Hc2kPz4",
    "external_id": "order_1042",
    "strategy": "cheapest",
    "tip_cents": 500
  }'

{
  "id": "del_7Qm3Xw9A",
  "status": "pending",
  "network": "doordash",
  "fee_cents": 1000,
  "tracking_url": "https://deliveree.online/t/del_7Qm3Xw9A"
}

Retrieve a delivery

GET/api/v1/deliveries/{id}

Returns the delivery object with its current status. Webhooks are the better way to follow a delivery; use this to check one on demand.

curl https://deliveree.online/api/v1/deliveries/del_7Qm3Xw9A \
  -H "Authorization: Bearer $DELIVEREE_API_KEY"

Cancel a delivery

POST/api/v1/deliveries/{id}/cancel

Asks the courier network to cancel. Returns the delivery object; its status is canceled if the cancel went through.

curl -X POST https://deliveree.online/api/v1/deliveries/del_7Qm3Xw9A/cancel \
  -H "Authorization: Bearer $DELIVEREE_API_KEY"

Statuses

Every delivery follows this flow and ends in one of three final states.

Webhooks

Give us an HTTPS URL and Deliveree will POST an event to it each time a delivery changes. Each event carries its type and the delivery it is about.

POST /webhooks/deliveree HTTP/1.1
Content-Type: application/json
Deliveree-Signature: t=1790101992,v1=<hex HMAC-SHA256 of "1790101992.<raw body>">

Verify signatures

Every webhook carries a Deliveree-Signature header of the form t=<unix>,v1=<hex>. v1 is the hex HMAC-SHA256 of the string t.body (the timestamp, a full stop, then the raw request body) keyed with your signing secret.

• Compute the HMAC over the raw body, before any JSON parsing.
• Compare in constant time, and reject old timestamps so a captured request cannot be replayed.
• Answer with any 2xx once you have stored the event.

import crypto from 'node:crypto'

const TOLERANCE_SECONDS = 300 // reject anything signed more than 5 minutes ago

/**
 * rawBody: the request body exactly as received (a string), before JSON.parse.
 * header:  the Deliveree-Signature header, e.g. "t=1790101992,v1=5f2c…"
 * secret:  your webhook signing secret.
 */
export function verifyDelivereeSignature(rawBody, header, secret) {
  const parts = {}
  for (const piece of String(header || '').split(',')) {
    const i = piece.indexOf('=')
    if (i > 0) parts[piece.slice(0, i).trim()] = piece.slice(i + 1).trim()
  }
  const t = Number(parts.t)
  if (!Number.isInteger(t) || !parts.v1) return false
  if (Math.abs(Date.now() / 1000 - t) > TOLERANCE_SECONDS) return false

  const expected = crypto
    .createHmac('sha256', secret)
    .update(`${parts.t}.${rawBody}`)
    .digest('hex')

  const a = Buffer.from(expected, 'hex')
  const b = Buffer.from(parts.v1, 'hex')
  return a.length === b.length && crypto.timingSafeEqual(a, b)
}

Not settled yet

This draft deliberately leaves these open. Tell us what you need.

• The error response format and error codes.
• Rate limits.
• How a partner key names the merchant a request is for.
• Whether fee_cents includes the dispatch fee or it is billed separately.
• How long a quote lasts, and whether booking the same external_id twice is safe.
• Whether a cancel after pickup is possible, and what the network charges for it.
• Webhook retries, and the order events arrive in.

Get access

Nothing here is self-serve yet. If you run an ordering platform and want to build against the draft, or you are a Boom Online Ordering restaurant waiting for the switch, email us and say which.