> For the complete documentation index, see [llms.txt](https://rwaperp-1.gitbook.io/rwaperp-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rwaperp-1.gitbook.io/rwaperp-docs/rwa-perp-b2b-api/rest-api-reference/trading-and-orders/get-v1-algo-orders.md). # get v1 algo orders `GET /v1/algo/orders` **Authentication:** RWA **Rate limit:** 5 requests per second ## Description Get algo order details by customized filters. For filter by status, one can reference special bundled statuses below for ease of access of Open (i.e `INCOMPLETE`) orders or `COMPLETED` orders. `INCOMPLETE` = `NEW` + `PARTIAL_FILLED` `COMPLETED` = `CANCELLED` + `FILLED` ## Parameters | Name | Location | Type | Required | Description | Example | | -------------- | -------- | ------ | -------- | -------------------------------------------------------------------------------------------------------- | ------- | | `symbol` | query | string | No | — | — | | `order_type` | query | string | No | `LIMIT`/`MARKET` | — | | `status` | query | string | No | `NEW`/`CANCELLED`/`PARTIAL_FILLED`/`FILLED`/`REJECTED`/`INCOMPLETE`/`COMPLETED` | — | | `order_tag` | query | string | No | Filter by the full stored order tag, including a current-format `enum::` tag. | — | | `start_t` | query | number | No | start time range that wish to query, noted the time stamp is 13-digits timestamp. | — | | `end_t` | query | number | No | end time range that wish to query, noted the time stamp is 13-digits timestamp. | — | | `page` | query | number | No | the page you wish to query. start from 1 | — | | `size` | query | number | No | the page size you wish to query (max: 500) | — | | `side` | query | string | No | `BUY`/`SELL` | — | | `algo_type` | query | string | No | Supported types are `STOP`, `TPSL`, `positional_TPSL` | — | | `is_triggered` | query | string | No | — | — | ## Responses ### HTTP 200 OK | Field | Type | Required | Description | | ------------------------------------- | -------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `success` | boolean | Yes | Indicates whether the request was successful. Example: `True` | | `timestamp` | integer | No | Server timestamp in milliseconds. Example: `1702989203989` | | `data` | object | Yes | — | | `data.meta` | object | Yes | — | | `data.meta.total` | integer | Yes | Example: `9` | | `data.meta.records_per_page` | integer | Yes | Example: `25` | | `data.meta.current_page` | integer | Yes | start from 1 Example: `1` | | `data.rows` | array | Yes | — | | `data.rows[].algo_order_id` | number | Yes | Example: `168400010` | | `data.rows[].algo_status` | string | Yes | Example: `NEW` | | `data.rows[].algo_type` | string | Yes | Example: `STOP` | | `data.rows[].fee_asset` | string | Yes | Example: `USDC` | | `data.rows[].is_triggered` | string | Yes | Example: `false` | | `data.rows[].order_tag` | string | Yes | Full tag stored on the algo order. Current custom-fee tags use `enum::`. Historical orders may contain a legacy `enum:` tag; do not rewrite it. Example: `enum:broker_b:GRID_PRO` | | `data.rows[].parent_algo_order_id` | number | Yes | Example: `0` | | `data.rows[].quantity` | number | Yes | Example: `5.5` | | `data.rows[].root_algo_order_id` | number | Yes | Example: `168400010` | | `data.rows[].root_algo_order_status` | string | Yes | Example: `NEW` | | `data.rows[].side` | string | Yes | Example: `BUY` | | `data.rows[].symbol` | string | Yes | Example: `PERP_NEAR_USDC` | | `data.rows[].margin_mode` | `CROSS` / `ISOLATED` | No | Example: `CROSS` | | `data.rows[].executed_quantity` | number | No | Example: `0` | | `data.rows[].total_executed_quantity` | number | Yes | Example: `0` | | `data.rows[].total_fee` | number | Yes | Aggregate fee across executed trades, including any custom trading fees. Use trade-level fields for reconciliation; this value is not a builder or affiliate payout basis. Example: `0` | | `data.rows[].trigger_price` | number | Yes | Example: `2.5` | | `data.rows[].trigger_price_type` | string | Yes | Example: `MARK_PRICE` | | `data.rows[].type` | string | Yes | Example: `MARKET` | | `data.rows[].created_time` | string | Yes | Example: `1702871974317` | | `data.rows[].updated_time` | string | Yes | Example: `1702871974317` | | `data.rows[].visible_quantity` | number | Yes | Example: `5.5` | | `data.rows[].realized_pnl` | number | No | Example: `0.0` | | `data.rows[].child_orders` | array | No | Array of `AlgoOrder` | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://rwaperp-1.gitbook.io/rwaperp-docs/rwa-perp-b2b-api/rest-api-reference/trading-and-orders/get-v1-algo-orders.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.