YO Protocol Documentation
Back to YO dApp
  • Welcome to YO
    • What is YO?
  • Why should I use YO?
  • FAQ
  • User Guides
    • How to Deposit into YO
  • How to Withdraw from YO
  • Protocol
    • YO Protocol
    • yoTokens
  • Contract Addresses
  • Security Audits
    • Immunefi Bug Bounty
  • Risks
  • API
  • Technical Guides
    • Deposit and Withdraw
  • Quick links
    • YO dApp
    • Follow us on X
    • Join our Telegram community
Powered by GitBook
On this page

API

PreviousRisksNextTechnical Guides

Last updated 1 month ago

YO Protocol API

Anyone can use the API to fetch historical information at the protocol or address-level.

Base URL: https://api.yo.xyz

Protocol-level data

Get a snapshot of the current TVL, yield, underlying pools and allocation of the protocol vaults.

Check the status of pending redeem requests for a given YO vault on a given blockchain.

Fetch the historical realized yield of a specific YO vault.

Fetch the historical TVL of a specific YO vault

User-level data

Fetch the historical deposits and withdrawals of a specific address for a specific YO vault on a specific blockchain.

get
Path parameters
vaultAddressstringRequired
networkstring · enumRequiredPossible values:
Responses
200Success
get
GET /api/v1/vault/{network}/{vaultAddress} HTTP/1.1
Host: 
Accept: */*
200Success

No content

Page cover image
get
Path parameters
vaultAddressstringRequired
networkstring · enumRequiredPossible values:
Header parameters
AcceptstringRequiredExample: application/json
Content-TypestringRequiredExample: application/json; charset=utf-8
Responses
200Success
application/json
Responseall of
and
get
GET /api/v1/vault/pending-redeems/{network}/{vaultAddress} HTTP/1.1
Host: 
Accept: application/json
Content-Type: application/json; charset=utf-8
200Success
{
  "data": {
    "raw": 1,
    "formatted": "text"
  },
  "message": "text",
  "statusCode": 200
}
get
Path parameters
vaultAddressstringRequired
networkstring · enumRequiredPossible values:
Header parameters
AcceptstringRequiredExample: application/json
Content-TypestringRequiredExample: application/json; charset=utf-8
Responses
200Success
get
GET /api/v1/vault/yield/timeseries/{network}/{vaultAddress} HTTP/1.1
Host: 
Accept: application/json
Content-Type: application/json; charset=utf-8
200Success

No content

get
Path parameters
vaultAddressstringRequired
networkstring · enumRequiredPossible values:
Header parameters
AcceptstringRequiredExample: application/json
Content-TypestringRequiredExample: application/json; charset=utf-8
Responses
200Success
get
GET /api/v1/vault/tvl/timeseries/{network}/{vaultAddress} HTTP/1.1
Host: 
Accept: application/json
Content-Type: application/json; charset=utf-8
200Success

No content

get
Path parameters
vaultAddressstringRequired
userAddressstringRequired
networkstring · enumRequiredPossible values:
Query parameters
limitnumberOptional
Header parameters
AcceptstringRequiredExample: application/json
Content-TypestringRequiredExample: application/json; charset=utf-8
Responses
200Success
get
GET /api/v1/history/user/{network}/{vaultAddress}/{userAddress} HTTP/1.1
Host: 
Accept: application/json
Content-Type: application/json; charset=utf-8
200Success

No content

  • YO Protocol API
  • Protocol-level data
  • GET/api/v1/vault/{network}/{vaultAddress}
  • GET/api/v1/vault/pending-redeems/{network}/{vaultAddress}
  • GET/api/v1/vault/yield/timeseries/{network}/{vaultAddress}
  • GET/api/v1/vault/tvl/timeseries/{network}/{vaultAddress}
  • User-level data
  • GET/api/v1/history/user/{network}/{vaultAddress}/{userAddress}