> For the complete documentation index, see [llms.txt](https://docs.openetf.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openetf.xyz/developers/api.md).

# OpenETF API

**The OpenETF API is the programmatic client of Managed Execution: a Manager's own strategies, bots or third-party terminals use it to trade the ETFs that Manager runs, with the same requests and checks as the Trading Terminal. It never hands out a Hyperliquid key or a signature.**

## One execution path for code and for people

A Manager who runs a strategy in code connects it to an ETF through the API instead of trading by hand. The API and the Trading Terminal submit the same kind of request, called an intent, pass the same checks, pay the same fees and draw on the same capacity, so moving from the Terminal to a bot needs no new signing key or trading wallet ([Managed Execution](https://docs.openetf.xyz/how-it-works/risk-controls/managed-execution.md#two-ways-in-one-path)).

## Credentials identify a fund, never sign for it

* Each OpenETF API credential belongs to one Manager and names the ETFs that Manager runs and the actions it may request for them.
* A credential can be revoked at any time. Revocation takes effect at once, before any request it approved is signed or sent.
* A credential is not a signing key. No response contains the fund's Trading Agent Wallet, a Hyperliquid native API key or a signature that could be broadcast elsewhere.

## Requests are checked, idempotent and recorded

An intent asks for one trading action on one ETF: an order, a cancel, a permitted leverage change or a defined movement between the fund's own balances. Before anything is signed, Managed Execution checks who is asking, what the action is, whether the market is one of the fund's [Supported Markets](https://docs.openetf.xyz/how-it-works/risk-controls/supported-markets.md), and whether the request still fits the fund's positions, open orders, reserved cash and restrictions ([Managed Execution](https://docs.openetf.xyz/how-it-works/risk-controls/managed-execution.md#checked-before-signing)).

Retrying a request never creates a second order. The exchange can still reject an order or fill it partially; a submission, a fill and a settled balance are separate facts, and each is recorded. When required data goes stale or a check cannot complete, requests that add risk are refused, and a reducing, cancelling or closing request goes through only when the service can show that it reduces risk; otherwise the service is Suspended and ordinary signing stops. A refused request comes back with its reason. Hyperliquid's rate limits apply to the fund's trading whichever client sends it, and the API carries no high-frequency latency commitment.

## What the API cannot do

* Move money out of the fund. Transfers to anyone else, withdrawals, staking, delegation and deposits into Hyperliquid Legacy Vaults are rejected, whatever a request calls itself.
* Act for an ETF its Manager does not run.
* Bypass a restriction, a removed market or cash reserved for waiting redemptions.

Manager-initiated fills through the API carry the same platform trading fee as the Terminal ([Fees and costs](https://docs.openetf.xyz/economics/fees.md)).

[Trading an ETF](https://docs.openetf.xyz/managing/trading.md) · [Building with OpenETF](https://docs.openetf.xyz/developers/integrations.md)
