Add Bitquery Hyperliquid API to APIs & Tools - #19
Open
divyasshree-BQ wants to merge 2 commits into
Open
Conversation
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Bitquery's Hyperliquid API to the APIs & Tools section.
The reason it may be worth a slot here rather than being another API wrapper: Bitquery serves Hyperliquid's order book at L3 (market-by-order) market-wide. Every book delta is a single order carrying its own order id and the wallet address that placed it.
l2BookBookUpdatesThe native API does expose order-level detail, but only for your own account (
orderUpdates,userFills); market-wide it serves aggregated L2. Because Hyperliquid settles on a transparent L1, the wallet behind each order is public — so this is L3 with named attribution, which does not exist on centralised venues, where exchanges anonymise L3 feeds. It makes market-maker tracking and cancel-to-fill analysis possible at all.Beyond the book: trades, OHLCV candles, liquidations, per-trader funding, positions, leverage updates, TWAPs, mark prices, price updates and raw signed actions. The same query runs as a historical query or a real-time subscription, and the archive shares one protobuf schema with the Kafka streams, so backtest and production code decode identically.
Happy to reword or move it to Analytics if that fits the list better.