> 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-portfolio-history-v1.md).

# GET /api/v1/account/portfolio-history

Account portfolio time-series.

`operationId`: `fetchPortfolioHistoryV1`

**Authentication:** `hmacAuth`.

Portfolio time-series for the authenticated account — equity, cumulative trading PnL, and cumulative traded volume — downsampled over the selected `window` (`day`, `week`, `month`, or `all`), oldest first. Extends `/account/equity-history` (equity only, \~1h window) with PnL and volume series across multiple windows; both endpoints derive equity from the same source, so the series never disagree.

## Parameters

| Name    | In    | Type      | Required | Description                                                                                                                                                                                                |
| ------- | ----- | --------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `None`  | None  | —         | No       | —                                                                                                                                                                                                          |
| `limit` | query | `integer` | No       | Maximum number of points to return. Capped server-side at the selected window's capacity (day 288, week 168, month 120, all 366); a larger value is clamped, not rejected. Omit to return the full window. |

## Responses

| Status | Body                                                                    | Meaning                                             |
| ------ | ----------------------------------------------------------------------- | --------------------------------------------------- |
| `200`  | [`PortfolioHistory`](/api-reference/guides/schemas.md#portfoliohistory) | Portfolio time-series for the window, oldest first. |
| `400`  | — *(no schema declared)*                                                | —                                                   |
| `401`  | — *(no schema declared)*                                                | —                                                   |
| `429`  | — *(no schema declared)*                                                | —                                                   |

## Example

```bash
curl -X GET 'https://exchange.nexus.xyz/api/exchange/api/v1/account/portfolio-history' \
  -H 'X-API-Key: nx_7f3a1b...' \
  -H 'X-Timestamp: 1776033911836' \
  -H 'X-Signature: <hmac-sha256>'
```

***

<sub>Generated from</sub> <sub></sub><sub>`eng/apps/exchange/api/openapi.json`</sub> <sub></sub><sub>(spec</sub> <sub></sub><sub>`0.9.27`</sub><sub>). Do not edit by hand — regenerate with</sub> <sub></sub><sub>`python3 product/docs/tools/api-reference/generate.py`</sub><sub>. Hand-authored context lives in the Guides pages.</sub>


---

# 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-portfolio-history-v1.md?ask=<question>&goal=<endgoal>
```

`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.