---
title: "Fetch Open Orders"
method: GET
path: "/v0/orders/open"
tags: ["Orders & Positions"]
---

# Fetch Open Orders

`GET /v0/orders/open`

List the wallet's resting orders that haven't filled or been cancelled yet. Each entry has the market, outcome, side, size, price, and time-in-force.

Filter by `venue` to scope to Polymarket, Opinion, or Limitless.

## Query parameters

- `address` string, required
- `venue` 'polymarket' | 'opinion' | 'limitless'

## Response `200`

Open orders list.

- OrderV0[]
  - `id` string, required — Unified order id. Stable across the order's lifetime; reuse it in `fetchOrderHosted` and `cancelOrderHosted`.
  - `side` 'buy' | 'sell', nullable — Order direction. `null` on cancel responses, which only carry id and status.
  - `type` 'market' | 'limit', nullable — Order type echoed from the build. `null` on cancel responses.
  - `amount` number, nullable — Order size in outcome shares. For market submits, this is the shares actually obtained (`tokens_bought` / `tokens_sold`); for resting limit orders it is the total shares originally requested. `null` on cancel responses.
  - `price` number, nullable — Limit price in probability units [0, 1] for limit orders. `null` for market orders and cancel responses.
  - `filled` number — Shares filled so far. For market submits this equals the shares obtained on-chain; for resting limit orders it is the running fill total.
  - `remaining` number — Shares still outstanding (`amount - filled`, floored at 0). Reaches 0 when the order is fully filled or cancelled.
  - `status` string, required — Lifecycle status. Open-order values include `resting` and `partial`; submit responses pass through the upstream status string (`failed` when an error was raised); cancel responses return the venue's cancel-acknowledgement status.
  - `fee` number, nullable — Total fee charged for this order, in USDC dollars. `null` until the venue reports fees (typically after settlement).
  - `timestamp` string, nullable — ISO-8601 timestamp the order was created on the venue side. `null` on cancel responses.
  - `tx_hash` string, nullable — On-chain settlement transaction hash on Polygon. `null` until the order settles on-chain (resting limit orders stay `null` until matched).
  - `chain` string, nullable — Chain the order settled on. Always `polygon` for hosted orders today (Opinion settles cross-chain via the same Polygon escrow). `null` on cancel responses.
  - `block_number` integer, nullable — Polygon block height at which the order settled. `null` until settlement.

## Other responses

- `401` — Invalid or missing PMXT API key.

## Changes

- **2026-06-24** `6784cc7c8376` — 1 info
  - added the new enum value `limitless` to the `query` request parameter `venue`
- **2026-06-09** `6c1e54fea3a3` — 2 info
  - api tag `Orders & Positions` added
  - api tag `Orders & Positions (Hosted)` removed
- **2026-06-09** `d2fae1223132` — 2 warning
  - removed the optional property `items/market_id` from the response with the `200` status
  - removed the optional property `items/outcome_id` from the response with the `200` status

[Change history](https://skmtc.dev/pmxt-dev/apis/pmxt-hosted-router-api/changes/v0/orders/open/get.md)

---

[API](https://skmtc.dev/pmxt-dev/apis/pmxt-hosted-router-api.md) · [All operations](https://skmtc.dev/pmxt-dev/apis/pmxt-hosted-router-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/pmxt-dev/pmxt-hosted-router-api/revisions/9ee3cbe2dc87/schema)