Get trades

Returns trade details where the requestor is the Platform, either party associated with the trade, or the account group where the trade was settled. For the party information, the asset is the settlement currency (i.e asset RECEIVED). This means in the second you are receiving USD correctly, 00SCXM is receiving BTC. The "sell" side receives the quoted currency, the "buy" side receives the underlying. Our trade structure mirrors a typical back office trade report (FIX TradeCaptureReport) and we use the concept of settlement currency for the sides to help keep our system agnostic of symbol definitions. Results are limited to the last 2 months

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
string

Filter by account label (e.g., general, sub_account_test). Account labels are used to categorize accounts under a participant. Each participant account_label maintains a separate balance and transaction history.

number
≥ 1

Page number for pagination (starts at 1).

string

Filters for trades within a designated market_identifier_code.

string

Filters for trades excluding those from a particular market_identifier_code.

string

Filters for trades based on the specific platform_code where the trade execution took place.

string

Filters for trades based excluding those from a particular platform_code.

string
enum

Filters for trades based on their current trade_state.

Allowed:
string
enum

Filters for trades based on their current settlement_state.

Allowed:
string

Filters for trades where the provided party_code is at least one of the counterparties to a trade in the parties array.

number

Filters for trades with a timestamp greater than the provided value, which can be defined in milliseconds or nanoseconds.

number

Filters for trades with a timestamp greater than or equal to the provided value, which can be defined in milliseconds or nanoseconds.

number

Filters for trades with a timestamp equal to the provided value, which can be defined in milliseconds or nanoseconds.

number

Filters for trades with a timestamp less than the provided value, which can be defined in milliseconds or nanoseconds.

number

Filters for trades with a timestamp less than or equal to the provided value, which can be defined in milliseconds or nanoseconds.

string

Filters for trades with the provided client_trade_id value.
Note:

  • Platforms integrated to the zerohash RFQ systems, the quote_id from the RFQ will be saved as the client_trade_id once the quote has been executed.
  • Platforms integrated to the zerohash CLOB, the execution_id from the order trade execution will be saved as the client_trade_id on the resulting trade.
string

Filters for trades with the provided execution_id in either party's execution_id field.

string

Filters for trades based on the reporting_party associated with each trade.

string

Filters for trades based on the settlement_schedule associated with each trade.

Headers
string
required

HMAC-SHA256 signature of the request, base64-encoded. See the Authentication guide for the exact signing formula.

string
required

Current Unix timestamp in seconds. Must be within 60 seconds of server time or the request is rejected.

Responses

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json