Sign in
Historical Data

Get Vault Historical APR

Changed on

Simple-rate (non-compound) APR per point over [from, to]. Each point annualizes share-price growth over effectiveIntervalSeconds, the real span between its two snapshots, which is at least the trailing apyInterval window (seconds) and can exceed it on a sparse series; points are spaced by step (granularity), independent of apyInterval. Reward APR is reserved for future rewards indexing and is always 0. Withheld series carry a machine-readable reason: INDEXING_NOT_STARTED or INDEXING_STALLED on 503 (both still resolvable, with a Retry-After hint), PROTOCOL_UNSUPPORTED on 404 (permanent — the vault's protocol has no price indexer, so no retry can ever succeed). Switch on reason rather than matching the error prose. The indexing-status endpoint reports the same state without erroring.

get/v2/opportunities/{chainId}/{vaultAddress}/historical/apr

Request

  • The document declares no server URL.
  • Auth: none declared

Path parameters

chainIdinteger required

EVM chain ID (e.g. 1 for Ethereum)

vaultAddressstring required

0x-prefixed 40-hex vault contract address

Query parameters

stepinteger

Point spacing (granularity) in seconds, at most 31536000 (365 days). Defaults to 86400 (1 day). The range may span at most 10,000 buckets at this step

apyIntervalinteger

APY/APR trailing window (lookback) in seconds, independent of step, at most 7776000 (90 days). Defaults to 2592000 (30 days)

startDatestring date-time required

Inclusive lower bound (RFC3339/ISO-8601). At most 365 days before now

endDatestring date-time

Inclusive upper bound (RFC3339/ISO-8601). Omit it — or send a future instant — to mean "the latest data available"; clients that want a live trailing series should do that rather than sending a client clock, so the query key stays stable while the answer keeps moving.

Response

OK

Changes

  • v28a7a742fa9bdRevision changes
    • warning

      for the query request parameter apyInterval, the max was set to 7776000.00

    • warning

      for the query request parameter step, the max was set to 31536000.00

  • v2d1bebce37c58Revision changes
    • info

      added the optional property // to the response with the status