Skip to main content
A fill record is created each time one of your orders executes against the book, in whole or in part. Call client.portfolio.fills() to retrieve the complete fill history for a subaccount, giving you a granular audit trail of every execution including instrument, side, price, quantity, and timestamp. This data underpins your trade reconciliation, PnL attribution, and post-trade reporting workflows.

Method

Endpoint: GET /v1/fills

Example

Parameters

string
The subaccount whose fill history to retrieve. Omit to retrieve fills across all subaccounts associated with your key.

Response

The endpoint returns a list of fill objects. Common fields:
string
Unique fill identifier.
string
The Molecule order ID that generated this fill.
integer
The venue-specific instrument that was executed.
"BUY" | "SELL"
Direction of the fill.
string
Execution price as a decimal string.
string
Executed quantity as a decimal string.
string
ISO 8601 timestamp of the fill event.

Accessing fills via the orders namespace

The same GET /v1/fills endpoint is also accessible as client.orders.fills(subaccount_id). Both methods call the same endpoint with the same parameters. Use whichever namespace fits your code organisation — portfolio.fills for post-trade analysis, orders.fills when working alongside order lifecycle methods.

Real-time fills

Subscribe to the /v1/ws/fills WebSocket stream to receive fill events as they occur, rather than polling this REST endpoint. See the WebSocket overview for connection details.