Dumpster Controls · agent page

This is the agent-optimized version of https://dumpstercontrols.io/help/api/orders-endpoints: the same content as the human page, without scripts, styles, animations or navigation. People should open the full page.

Canonical page
https://dumpstercontrols.io/help/api/orders-endpoints
Last updated
2026-08-22
Tokens
799 tokens (cl100k_base), within the 2,500-token budget for a help page
Size
7.0 KB for this page, against 23 KB for the human page (69% smaller)
Markdown
https://dumpstercontrols.io/help/api/orders-endpoints.md, or send Accept: text/markdown to the canonical URL
Cite as
Orders endpoints: list and read orders. Dumpster Controls. https://dumpstercontrols.io/help/api/orders-endpoints (accessed 2026-11-16).
More for agents
Facts sheet · llms.txt · llms-full.txt · All agent pages · Product manual

Developer API · updated 2026-08-22

Orders endpoints: list and read orders

Two endpoints expose your orders: a paginated list with filters, and a single-order lookup by order number. Fields mirror what the app shows, minus anything internal or sensitive.

  1. ## List orders
    ```
    GET /v1/orders
    ```
    Query parameters: status (one of placed, confirmed, scheduled, out_for_delivery, delivered, waiting_pickup, picked_up, completed, canceled, waiting_delivery, waiting_landfill), from and to (YYYY-MM-DD, filtering created_at), page (default 1) and per_page (default 25, max 100). Results come newest first.
    ```
    curl -H "Authorization: Bearer dc_live_..." \
    "https://gcwyoiihrupbfqqlcurh.supabase.co/functions/v1/api-v1/v1/orders?status=completed&from=2026-08-01&per_page=50"
    ```
  2. ## Read one order
    ```
    GET /v1/orders/{order_number}
    ```
    Order numbers are the same ones you see in the app (for example 1042). A number that does not exist in YOUR company returns 404, even if it exists elsewhere: data never crosses companies.
  3. ## The order object
    Each order carries: order_number, status, payment_status, delivery_date, pickup_date, rental_days, address (line1, city, state, zip), size (the dumpster size label), debris_type, total_price, base_price, landfill_cost, net_weight_tons, customer_ref (the customer id, joinable against /v1/customers), created_at and completed_at. All money fields are US dollars as decimal numbers, not cents.
    payment_status is one of: unpaid, paid, refunded, no_charge. no_charge means the order has no billing phase: no invoice, nothing owed. Treat it as a terminal financial state, never as an unpaid balance.
  4. ## What is intentionally NOT exposed
    Internal identifiers, tracking tokens, profit figures, GPS coordinates, risk-review state and demo data never appear in API responses. Orders under fraud review are hidden entirely until released.
  5. ## Pagination pattern
    Loop pages while has_more is true:
    ```
    page 1 -> has_more true -> request page 2 -> ... -> has_more false, done.
    ```
    Keep per_page at 100 for backfills to minimize calls (relevant inside the free window).

Related guides

© 2026 Dumpster Controls. All rights reserved. Made in the USA.