How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

THORChain History API

The History API from THORChain — 12 operation(s) for history.

THORChain History API is one of 65 APIs that THORChain publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include History. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 12 operations across 12 paths, and defines 45 schemas. It is described by OpenAPI 3.2.0, at version 3.19.1.

Requests are made against a single base URL, https://gateway.liquify.com/chain/thorchain_api.

12 operations 12 paths 45 schemas 12 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.19.1
Base URL
https://gateway.liquify.com/chain/thorchain_api
Resource Areas
1

Paths & Operations 12

Across 12 paths, the API surfaces 12 operations — 12 GET. Each is listed below with its method, path, parameters, and response codes.

History 12
GET
/v2/history/affiliate
Affiliate earnings History
GetAffiliateHistory 5 params → 200
GET
/v2/history/affiliate/earnings
Affiliate Liquidity Fee Earnings History
GetAffiliateEarning 5 params → 200
GET
/v2/history/affiliate/stats
Affiliate Volume Stats
GetAffiliateStats 5 params → 200
GET
/v2/history/depths/{pool}
Depth and Price History
GetDepthHistory 5 params → 200
GET
/v2/history/earnings
Earnings History
GetEarningsHistory 4 params → 200
GET
/v2/history/liquidity_changes
Liquidity Changes History
GetLiquidityHistory 5 params → 200
GET
/v2/history/reserve
Reserve income and expenses over bucketed history
GetReserveHistory 4 params → 200
GET
/v2/history/rune
Rune price history in USD
GetRunePriceHistory 4 params → 200
GET
/v2/history/runepool
RUNEPool total members and units History
GetRUNEPoolHistory 4 params → 200
GET
/v2/history/savers/{pool}
Savers Units and Depth History
GetSaversHistory 5 params → 200
GET
/v2/history/swaps
Swaps History
GetSwapHistory 5 params → 200
GET
/v2/history/tvl
Total Value Locked History
GetTVLHistory 4 params → 200

Schemas 45

The contract defines 45 schemas that model the data the API accepts and returns. The most detailed are SwapHistoryItem (48 properties), DepthHistoryItem (16 properties), DepthHistoryMeta (14 properties), LiquidityHistoryItem (12 properties). Each schema is shown below with its type and property counts.

TVLHistoryIntervals
array
AffiliateHistoryItem
object
6 properties 6 required
DepthHistoryIntervals
array
ReserveIntervals
array
RUNEPoolHistory
object
2 properties 2 required
DepthHistoryItem
object
16 properties 12 required
EarningsHistoryIntervals
array
AffiliateEarningItem
object
4 properties 4 required
TVLHistoryItem
object
7 properties 5 required
RunePriceHistory
object
2 properties 2 required
AffiliateStatItem
object
3 properties 3 required
RUNEPoolHistoryItem
object
5 properties 4 required
RunePriceItem
object
3 properties 3 required
ItemThorname
object
4 properties 4 required
RUNEPoolHistoryIntervals
array
RunePriceIntervals
array
SwapHistory
object
2 properties 2 required
ReserveHistory
object
2 properties 2 required
LiquidityHistoryIntervals
array
AffiliateStatsItem
object
5 properties 5 required
ReserveItem
object
5 properties 5 required
RUNEPoolHistoryMeta
object
6 properties 6 required
LiquidityHistoryItem
object
12 properties 12 required
SaversHistoryMeta
object
8 properties 8 required
RunePriceMeta
object
4 properties 4 required
SwapHistoryIntervals
array
LiquidityHistory
object
2 properties 2 required
DepthHistory
object
2 properties 2 required
EarningsHistory
object
2 properties 2 required
DepthHistoryMeta
object
14 properties 14 required
AffiliateHistoryIntervals
array
AffiliateHistoryMeta
object
5 properties 5 required
AffiliateEarning
array
SaversHistory
object
2 properties 2 required
AffiliateStats
array
EarningsHistoryItemPool
object
pool earnings data during the time interval
7 properties 7 required
EarningsHistoryItem
object
10 properties 10 required
DepthHistoryItemPool
object
2 properties 2 required
AffiliateHistory
object
2 properties 2 required
SaversHistoryItem
object
5 properties 5 required
AffiliateEarningInterval
object
6 properties 6 required
ReserveMeta
object
5 properties 5 required
TVLHistory
object
2 properties 2 required
SwapHistoryItem
object
48 properties 48 required
SaversHistoryIntervals
array

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

thorchain-history-api-openapi.yml Raw ↑

Other APIs THORChain publishes across the network.

THORChain Actions API
THORChain AGENTS.md API
THORChain Auth API
THORChain Balance API
THORChain Bank API
THORChain Block API
THORChain Bonds API
THORChain Borrower API
THORChain Borrowers API
THORChain Churns API
THORChain Clout API
THORChain Codes API
Where this information came from

This is an independent, third-party profile of THORChain History API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.