---
title: "Get Active Orders"
method: POST
path: "/trading/orders/active"
tags: ["Trading"]
---

# Get Active Orders

`POST /trading/orders/active`

Get currently active (in-flight) orders from exchange connectors.

Fetches real-time order data directly from the connectors' in-flight order tracking.
This shows orders that are currently open, pending, or partially filled on the exchanges.
Unlike /orders/search which queries historical data, this endpoint provides live order state.

Active orders include those in states: PENDING_CREATE, OPEN, PARTIALLY_FILLED, PENDING_CANCEL.
Orders that are fully filled, cancelled, or failed will not appear here (use /orders/search instead).

The response uses cursor-based pagination. Orders are sorted by client_order_id for consistency.

## Request body

- ActiveOrderFilterRequest — Request model for filtering currently active (in-flight) orders. Used to query orders that are currently open or pending on exchanges. All filters are optional - omitting a filter includes all values for that field. Example: ```json { "account_names": ["main"], "connector_names": ["binance"], "trading_pairs": ["BTC-USDT"], "limit": 50 } ```
  - `limit` integer — Maximum number of items to return per page. Range: 1-1000. Default: 100.
  - `cursor` string, nullable — Pagination cursor from a previous response's `next_cursor`. Omit for the first page. Pass the `next_cursor` value to fetch the next page.
  - `account_names` string[], nullable — Filter by account names. If omitted, queries all accounts.
  - `connector_names` string[], nullable — Filter by connector names (e.g., ['binance', 'binance_perpetual']). If omitted, queries all connectors.
  - `trading_pairs` string[], nullable — Filter by trading pairs (e.g., ['BTC-USDT', 'ETH-USDT']). If omitted, queries all pairs.

## Response `200`

Successful Response

- PaginatedResponse — Generic paginated response wrapper for list endpoints. Contains the requested data items and pagination metadata for fetching additional pages. Example: ```json { "data": [ {"order_id": "abc123", "status": "FILLED"}, {"order_id": "def456", "status": "OPEN"} ], "pagination": { "limit": 100, "has_more": true, "next_cursor": "1705123456789:def456", "total_count": 500 } } ```
  - `data` object[], required — Array of result items. Structure depends on the specific endpoint.
  - `pagination` object, required — Pagination metadata containing: `limit` (items per page), `has_more` (boolean, true if more results exist), `next_cursor` (string, pass to cursor param for next page, null if no more pages), `total_count` (total items matching the query across all pages).

## Other responses

- `422` — Validation Error

## Changes

- **2025-12-20** `1005bcd47280` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/hummingbot/apis/hummingbot-api/changes/trading/orders/active/post.md)

---

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