> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qfex.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Account execution history

> Retrieve funding payments, fee rebates and referral rewards, and use the correct timestamp formats.

Use the authenticated [`GET /executions` REST endpoint](https://docs.qfex.com/api-reference/rest/user/read-executions) on `https://api.qfex.com` to retrieve **settled account balance movements**, including funding payments (`funding`), fee rebates (`fee_rebate`), and referral rewards (`referral_reward`). Deposits, withdrawals and other supported execution types are also returned.

This endpoint provides **your account's funding payments**, not historical funding rates by product. For the live implied rate, use the [WebSocket funding stream](https://docs.qfex.com/websocket/channels/mds/funding_rate.md).

## Filter executions

The optional `execution_type` query parameter accepts a comma-separated list. For example, this query returns funding payments, rebates, and referral rewards in a UTC time window:

```bash theme={null}
curl -G 'https://api.qfex.com/executions' \
  --data-urlencode 'execution_type=funding,fee_rebate,referral_reward' \
  --data-urlencode 'start_time=2026-11-01T00:00:00Z' \
  --data-urlencode 'end_time=2026-11-09T23:59:59Z'
```

Add your normal [authentication credentials](https://docs.qfex.com/api-reference/api-keys.md) to the request. Both time filters are inclusive.

## Timestamp formats

> [!NOTE]
>
> **Response and request timestamps use different formats.**

* **Response:** `data[].created_at` is a **Unix timestamp in seconds**, potentially with fractional seconds (for example, `1731000000.123456`). It is a number, not an ISO 8601 string.
* **Request:** `start_time` and `end_time` accept **date/time strings**. Prefer an explicit UTC RFC 3339 / ISO 8601 value such as `2026-11-09T12:34:56Z`. Date-only forms such as `2026-11-09` are also accepted.
* **Not accepted:** passing a Unix timestamp (for example, `1731000000`) as either time-filter parameter produces HTTP `422 Unprocessable Entity`.

Convert `created_at` to a formatted UTC timestamp before reusing it as `start_time` or `end_time`. The endpoint currently does **not** accept epoch seconds as input.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.