> For the complete documentation index, see [llms.txt](https://docs.yo.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yo.xyz/integrations/api/v2-migration.md).

# V2 Migration

The YO API has moved to a new server and its public routes have changed.

* **New base URL:** `https://api-v2.yo.xyz`
* **Previous base URL:** `https://api.yo.xyz`
* **Migration deadline:** September 30, 2026

The previous API will remain available through September 30, 2026. Update your integration before the deadline; the previous backend will be unavailable afterward.

### Endpoint changes

#### Vault snapshot

* Previous: `GET /api/v1/vault/{network}/{vaultAddress}`
* API v2: `GET /v1/vaults/{slug}`

#### APY history

* Previous: `GET /api/v1/vault/yield/timeseries/{network}/{vaultAddress}`
* API v2: `GET /v1/vaults/{slug}/timeseries/apy`

#### TVL history

* Previous: `GET /api/v1/vault/tvl/timeseries/{network}/{vaultAddress}`
* API v2: `GET /v1/vaults/{slug}/timeseries/tvl`

#### User history

* Previous: `GET /api/v1/history/user/{network}/{vaultAddress}/{userAddress}`
* API v2: `GET /v1/history?family={slug}&user={walletAddress}&chainId={chainId}`

#### Pending redemptions

* Previous: `GET /api/v1/vault/pending-redeems/{network}/{vaultAddress}/{userAddress}`
* API v2: `GET /v1/users/{walletAddress}/pending-redeems?family={slug}`

#### User performance

* Previous: `GET /api/v1/performance/user/{network}/{vaultAddress}/{userAddress}`
* API v2: `GET /v1/performance/{walletAddress}?family={slug}`

The previous vault-wide pending-redemptions endpoint has no vault-wide equivalent in API v2. Use the wallet endpoint instead:

```http
GET /v1/users/{walletAddress}/pending-redeems?family={slug}
```

### What changed

#### Vault identifiers

Vault endpoints now use a vault-family `slug` instead of `network` and `vaultAddress` path parameters.

```http
GET https://api-v2.yo.xyz/v1/vaults/yousd
```

Existing vault-family identifiers: 

* yousd
* yoeth
* yobtc
* yoeur
* yogold
* yousd-edge

#### APY and TVL history

Both timeseries endpoints accept these optional query parameters:

* `from`: start date or timestamp
* `to`: end date or timestamp
* `interval`: `raw`, `hour`, or `day` (default: `day`)
* `limit`: maximum number of results, from 1 to 5,000 (default: 1,000)

```http
GET https://api-v2.yo.xyz/v1/vaults/yousd/timeseries/apy?interval=day
GET https://api-v2.yo.xyz/v1/vaults/yousd/timeseries/tvl?interval=day
```

#### User history

User history filters have moved from path parameters to query parameters. Use `family`, `user`, and `chainId` to reproduce a previous user-and-vault request.

```http
GET https://api-v2.yo.xyz/v1/history?family=yousd&user=0x...&chainId=8453
```

The endpoint also supports `type`, `period`, `cursor`, and `limit` filters.

#### Pending redemptions and performance

These endpoints are now wallet-scoped. Use the optional `family` query parameter to restrict the response to one vault family.

```http
GET https://api-v2.yo.xyz/v1/users/0x.../pending-redeems?family=yousd
GET https://api-v2.yo.xyz/v1/performance/0x...?family=yousd
```

### Response formats

API v2 uses new response schemas. Updating only the base URL is not sufficient: update the route, parameters, and response parsing for each migrated operation.


---

# 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.yo.xyz/integrations/api/v2-migration.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.