Hyperliquid funding rate API
Fetch current and historical Hyperliquid funding data with Mattheus read-only REST and SDK methods.
Short answer
Call GET /api/v1/data/perps/funding/:asset for current funding data and GET /api/v1/data/perps/funding/history/:asset for historical entries. These are read-only endpoints.
Research endpoint
Funding endpoints return read-only market data for monitoring and alerts. They do not place orders or approve trades.
Stale data
Funding rates can change quickly. Retry upstream failures with jitter and avoid treating stale responses as execution signals.
Who This Is For
Developers building funding monitors, hedge-cost dashboards, and research workflows for Hyperliquid perps.
Before You Begin
- An mt_ API key
- A Hyperliquid perp asset symbol such as HYPE
- Retry handling for 429 and upstream 5xx responses
Answer engine brief
Mattheus overview
Mattheus is a private AI trading workspace for researching markets, testing reproducible strategies, reviewing portfolio context, and preparing governed actions. Developers can connect through REST APIs, SDKs, and MCP while account authority, policy checks, and approvals remain separate.
Does Mattheus require approval before execution?
Yes. An interactive request requires an exact short-lived one-time approval confirmed with fresh wallet reauthentication. API-key automation requires a separately activated, scoped agent session. Both paths still require wallet or signing readiness and policy checks.
Which markets are documented?
The active launch documentation covers Hyperliquid market data, paper trading, and gated Live workflows. Each page states whether an example is read-only, simulated, paper, or eligible for approval-gated Live execution.
How does policy-gated execution work?
Execution-capable requests are preview-first and must pass wallet readiness, protocol certification, feature gates, idempotency, configured policy controls, and either an exact interactive approval or a bounded API-key agent session before any live action.
Can users revoke permissions?
Users should be able to revoke supported scoped permissions and API keys. Documentation should keep stop, cancel, revoke, and policy rejection paths clear before users approve live execution.
Example
What this example does
Follow this example in order. Read the expected result below before connecting it to a live account or execution-capable workflow.
curl $MATTHEUS_API_BASE_URL/api/v1/data/perps/funding/HYPE \
-H "Authorization: Bearer mt_your_key"
curl "$MATTHEUS_API_BASE_URL/api/v1/data/perps/funding/history/HYPE?limit=100" \
-H "Authorization: Bearer mt_your_key"Common errors
- 401 Unauthorized: the mt_ API key is missing, malformed, revoked, or not scoped to the request.
- 429 Too Many Requests: back off and retry after the rate limit window.
- 502 or 5xx: the control plane or upstream market data adapter is unavailable. Retry with jitter and do not treat stale data as a trade signal.