Exponential History API

The History API from Exponential — 1 operation(s) for history.

Operations 1

GET /api/v1/history/user/{network}/{vaultAddress}/{userAddress} Fetch the historical deposits and withdrawals of a specific address for a specific YO vault on a specific blockchain. #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/exponential-history-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

exponential-history-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Yo Protocol History API
  version: '1.0'
  description: 'Public read API for the YO Protocol (by Exponential.fi). Fetch historical and current protocol- and address-level data for yoVaults: current snapshot (TVL, yield, underlying pools, allocation), pending redeem requests, historical yield and TVL time series, per-user deposit/withdraw history, per-user pending redemptions, and per-user P&L. No API key required. Endpoints are assembled verbatim from the per-endpoint OpenAPI fragments published on the docs API reference page.'
servers:
- url: https://api.yo.xyz
  description: Production
tags:
- name: History
paths:
  /api/v1/history/user/{network}/{vaultAddress}/{userAddress}:
    get:
      operationId: HistoryController_getAggregatedHistory_v1
      summary: Fetch the historical deposits and withdrawals of a specific address for a specific YO vault on a specific blockchain.
      tags:
      - History
      parameters:
      - name: vaultAddress
        required: true
        in: path
        schema:
          type: string
      - name: userAddress
        required: true
        in: path
        schema:
          type: string
      - name: limit
        required: false
        in: query
        schema:
          type: number
      - name: network
        required: true
        in: path
        schema:
          enum:
          - base
          - ethereum
          - unichain
          - arbitrum
          - tac
          - plasma
          - hyperevm
          type: string
      responses:
        '200':
          description: ''