Async Hyperliquid
async-hyperliquid is a typed, asynchronous Python client for the Hyperliquid
REST API. It provides credential-free market and account queries through
InfoClient, plus authenticated order workflows through AsyncHyperliquid.
The client uses aiohttp, keeps protocol-shaped responses as TypedDict, and
supports explicit mainnet and testnet routing.
Installation
pip install async-hyperliquid
Read market data
import asyncio
from async_hyperliquid import InfoClient
from async_hyperliquid.types import Network
async def main() -> None:
async with InfoClient(network=Network.MAINNET) as client:
print(await client.mid_price("BTC"))
asyncio.run(main())
Place a testnet order
Use a dedicated API-wallet key and start on testnet. This submits a signed market order.
import asyncio
import os
from async_hyperliquid import AsyncHyperliquid
from async_hyperliquid.types import Network
async def main() -> None:
async with AsyncHyperliquid(
os.environ["HL_ACCOUNT_ADDRESS"],
os.environ["HL_SIGNING_KEY"],
network=Network.TESTNET,
) as client:
result = await client.place_order("BTC", True, 0.001, 0, is_market=True)
if result["status"] == "err":
raise RuntimeError(result["response"])
status = result["response"]["data"]["statuses"][0]
if isinstance(status, dict) and "error" in status:
raise RuntimeError(status["error"])
print(status)
asyncio.run(main())
Learn more in the Read the Docs documentation, API reference, migration guide, changelog, and license.
Benchmarks
The overall signing benchmark values below are from a parity-gated 1.0.0rc1
local CPU reference run. They are not network latency or exchange throughput.
See the detailed benchmarks/README.md manual for the
full methodology, parity gate, and per-operation results.
| Library | Geometric-mean throughput | Relative to SDK |
|---|---|---|
| async-hyperliquid | 24,641 ops/s | 1.460x |
| Official SDK | 16,874 ops/s | 1.000x |
| CCXT | 803 ops/s | 0.0476x |
The geometric mean gives each of the five operations equal weight, preventing
the faster action_hash workload from dominating the score.
1 maintainer
Metadata
1 maintainer
Release files for async-hyperliquid 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| async_hyperliquid-1.1.0.tar.gz | 363.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| async_hyperliquid-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 402.3 kB
Release files / async_hyperliquid-1.1.0.tar.gz
| Download URL | async_hyperliquid-1.1.0.tar.gz |
|---|---|
| Size | 363.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a4eed7cef67f720dabac07c5c364101215dc3ddc10e3341eb19fef553206ef2c
|
|
BLAKE2b-256 checksum How to use checksums |
8ddc8c3714799b85d25dc70160a9b8e291d53a55e5905e1bd4f209042ffb960d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 14, 2026.
Transparency logRelease files / async_hyperliquid-1.1.0-py3-none-any.whl
| Download URL | async_hyperliquid-1.1.0-py3-none-any.whl |
|---|---|
| Size | 38.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9ad3bfd0a3ee431bbca72697bb71353c7c771d0e681eafb66cc34421e419f423
|
|
BLAKE2b-256 checksum How to use checksums |
08fab3090d57c7112ec622a73a409f2a2548b89b454147972b6ab11bddcf85d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 14, 2026.
Transparency log
