> For the complete documentation index, see [llms.txt](https://docs.nexus.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexus.xyz/api-reference/account/fetch-fills-v1.md). # GET /api/v1/fills List your fills List your fills. `operationId`: `fetchFillsV1` · CCXT method: `fetchMyTrades` > **Declared server:** `https://api.testnet.nexus.xyz`. Examples follow the OpenAPI operation, path-item, then document server precedence and append the full operation path. A declared URL is not proof of live routing; verify the target deployment before use. See [Networks](/api-reference/guides/networks.md). **Authentication:** `hmacAuth`. Returns up to 1000 fills for the authenticated account, newest first. Fills are trade executions resulting from order matches — each fill carries the matched price, quantity, fee, and whether it was the taker or maker side. ## Parameters | Name | In | Type | Required | Default | Description | | ---------- | ----- | --------- | -------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `limit` | query | `integer` | No | `100` | Fills per page (default 100, capped at the 1,000-fill retained window). Bounds one page, not a cursor walk — see “Cursor pagination”. | | `order_id` | query | `string` | No | — | Return only the fills of this order. Exact match; an id that matches nothing returns an empty array rather than a 404. Narrows the same 1,000-fill retained window the unfiltered call serves, so fills that have aged out of that window are not reachable through it. One caveat worth knowing: a self-trade is served as a single netted row carrying the taker leg’s `order_id`, so filtering on the maker side of your own self-trade matches nothing. | | `cursor` | query | `string` | No | — | Opaque pagination cursor returned in the previous response's `X-Next-Cursor` header. Omit to fetch the first page. Treat the token as opaque: its format is not part of the contract and may change. Cursors do not expire. A malformed (unparseable) cursor is not an error — the server serves the first page. A well-formed cursor whose exact position has since been evicted from the retained window is not reset to the first page: pagination resumes at the nearest surviving boundary, so a resumed response is a continuation, not a fresh first page. A cursor is not bound to an operation or an account, so use it only with the operation that issued it. See “Cursor pagination” in the API description for how a walk terminates and what it does and does not guarantee. | ## Responses | Status | Body | Meaning | | ------ | -------------------------------------------------------- | ---------------------------- | | `200` | array of [`Fill`](/api-reference/guides/schemas.md#fill) | Array of fills, newest first | | `401` | — *(no schema declared)* | — | | `429` | — *(no schema declared)* | — | ## Example {% tabs %} {% tab title="cURL" %} ```bash curl -X GET 'https://api.testnet.nexus.xyz/api/v1/fills' \ -H 'X-API-Key: nx_7f3a1b...' \ -H 'X-Timestamp: 1776033911836' \ -H 'X-Signature: ' ``` {% endtab %} {% tab title="Python" %} ```python import requests headers = { "X-API-Key": "nx_7f3a1b...", "X-Timestamp": "1776033911836", "X-Signature": "" } response = requests.get("https://api.testnet.nexus.xyz/api/v1/fills", headers=headers) response.raise_for_status() print(response.json()) ``` {% endtab %} {% tab title="TypeScript" %} ```typescript const response = await fetch("https://api.testnet.nexus.xyz/api/v1/fills", { method: "GET", headers: { "X-API-Key": "nx_7f3a1b...", "X-Timestamp": "1776033911836", "X-Signature": "" }, }); if (!response.ok) throw new Error(`${response.status} ${await response.text()}`); console.log(await response.json()); ``` {% endtab %} {% endtabs %} `X-Signature` is a placeholder: it is derived from this specific request. See [Authentication](/api-reference/guides/authentication.md) for the canonical string and the HMAC rule. *** Generated from `eng/apps/exchange/api/openapi.json` (spec `0.9.70`). Do not edit by hand — regenerate with `python3 product/docs/tools/api-reference/generate.py`. Hand-authored context lives in the Guides pages. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.nexus.xyz/api-reference/account/fetch-fills-v1.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.