GDAX订单状态及含义问询：求完整状态列表与释义

Great question—this is a common frustration since the official GDAX (now Coinbase Pro) API docs don’t fully enumerate all order states. After digging through community discussions, API responses, and client implementations, here’s a consolidated breakdown of all confirmed states and their meanings, plus clarity on the settled field:

Confirmed Order States #

• pending: The order has been submitted to the system but hasn’t yet been added to the order book. This applies to orders waiting for initial validation, or conditional orders (like stop/limit) that haven’t triggered yet.
• active: The order is live on the order book and available to be matched with opposing orders. In many cases, this is used interchangeably with open, though some edge cases distinguish it as the "actively waiting" state post-pending.
• open: Essentially synonymous with active in most contexts—indicates the order is in the order book and eligible for matching, with no completion or cancellation action taken yet.
• done: A catch-all state for orders that are no longer active. To get specifics, check the reason field in the API response, which will be one of:
  • filled: The order was completely executed (all requested quantity matched)
  • canceled: The order was manually canceled by the user
  • rejected: The order was rejected by the system (e.g., insufficient funds, price outside allowed bounds, invalid parameters)
  • expired: The order reached its set time-to-live (TTL) and was automatically removed

Clarification on settled #

As you suspected, settled is not an order state—it’s a separate boolean field in the order object. It indicates whether all filled portions of the order have been fully cleared and settled into your account. When settled is true, you can freely use the funds or assets from the completed trades (no pending hold left).

A quick note on client implementations: Even though official clients use weak types, non-official ones (like Java/Rust) that use strings are mapping directly to these states, and the Haskell client’s enum aligns with this list—its lack of documentation is just an oversight, not a deviation from the actual API behavior.

内容的提问来源于stack exchange，提问作者Max