For the complete documentation index, see llms.txt. This page is also available as Markdown.

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:

What changed

Vault identifiers

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

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)

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.

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.

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.

Last updated