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

# Account APY

> Fetch the latest annual percentage yield for an account via the REST API

Equivalent to SDK's `client.amplify.vaults.getApys()` — see [SDK AI Reference](/v1.0.0/intro/products/earn/developers/sdk-ai-reference).

## Endpoint

```
GET https://api.paxoslabs.com/v2/amplify/vaultApys
```

APY points are derived from the vault's exchange-rate updates: each point at time `t` annualizes the rate change over the window `[t - lookback, t]`. Missing rates at a window boundary are linearly interpolated from the nearest updates (within 24h), or the most recent rate is carried forward. If a lookback window reaches back past a vault's first rate update, the window clamps to that first update and the APY annualizes over the vault's actual life.

## Query Parameters

| Parameter | Type | Required | Description |
| - | - | - | - |
| `filter` | `string` | No | Optional filter, e.g. `vaultAddress=0x...`. Omit to return all accessible vaults. |
| `startTime` | `string` | No | Start of the point range (RFC 3339 UTC). Default: 30 days before `endTime`. |
| `endTime` | `string` | No | End of the point range (RFC 3339 UTC). Default: now; clamped to now if in the future. |
| `interval` | `string` | No | Spacing between APY points: `1d`, `1w`, `1m`, `1y`. Default: `1d`. |
| `lookback` | `string` | No | Width of each point's rate window: `1d`, `7d`, `14d`, `30d`. Default: `7d`. |
| `orderByTimestamp` | `string` | No | Sort order: `desc` (newest first) or `asc` (oldest first). Default: `asc`. |
| `pageSize` | `int` | No | Results per page. With `orderByTimestamp=desc`, `1` returns the latest point; the default ascending order returns the oldest. |

## Example Request

```bash theme={null}
VAULT_ADDRESS="0x..."
curl -s "https://api.paxoslabs.com/v2/amplify/vaultApys?filter=vaultAddress%3D${VAULT_ADDRESS}&orderByTimestamp=desc&pageSize=1" \
  -H "x-api-key: $AMPLIFY_API_KEY" | jq '.vaultApys[0]'
```

## Response

```json theme={null}
{
  "vaultApys": [
    {
      "vaultAddress": "0x...",
      "chainId": 1,
      "timestamp": "2026-01-15T12:00:00Z",
      "interval": "1d",
      "apy": "5.2300"
    }
  ]
}
```

## Response Types

| Field | Type | Description |
| - | - | - |
| `vaultAddress` | `address` | BoringVault address |
| `chainId` | `number` | Chain the point belongs to |
| `timestamp` | `string` | RFC 3339 UTC timestamp of the APY point |
| `interval` | `string` | Spacing between points (echoes the request, e.g. `1d`) |
| `apy` | `string` | APY in percent (e.g., `"5.2300"` = 5.23%) |

<Info>
  The `apy` field is already a percentage (e.g., `5.2300` = 5.23%). Do not
  multiply by 100.
</Info>

<Info>
  **Vaults deployed on more than one chain** report a single chain's APY:
  Ethereum if the vault is deployed there, otherwise the lowest-numbered
  mainnet (or the lowest-numbered chain if every deployment is a testnet).
  `chainId` on each point tells you which chain was used.
</Info>


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