Arbitrum API Documentation
Overview
In this section we will see how to fetch data on different tokens, transactions, and DEXs like GMX on Arbitrum via APIs and Streams.
If you need help getting data on Arbitrum, reach out to support.
What is Arbitrum API?
Bitquery Arbitrum APIs help you fetch onchain data like trades, transactions, balances, token holders etc using graphQL query.
What are capabilities of Bitquery Arbitrum API?
Bitquery Arbitrum APIs are very flexible, you can fetch trade, transaction, and balance information for a period, for a specific wallet, and join with other information.
Difference between Arbitrum RPC and Bitquery Arbitrum API?
| Arbitrum RPC | Bitquery Arbitrum API |
|---|---|
| JSON-RPC endpoint exposing raw EVM on-chain state and transactions | GraphQL endpoint over pre-indexed, parsed Arbitrum data (token transfers, DEX trades, logs, calls, etc.) |
| No built-in history or analytics—any indexing/aggregation you build or outsource | Historical data, joins, aggregations & real-time subscriptions |
| Ideal for submitting transactions | Great for real-time data and historical backtesting without running your own indexer |
Does Bitquery support Arbitrum Websocket and Webhooks?
Bitquery supports websocket and webhooks; you can convert most GraphQL APIs into GraphQL streams by changing the word query to subscription. You can monitor this data via a websocket. More docs and code samples are available here.
Quick start
Run this minimal GraphQL query to fetch the latest 5 DEX trades on Arbitrum:
query LatestArbitrumTrades {
EVM(network: arbitrum) {
DEXTrades(limit: { count: 5 }, orderBy: { descending: Block_Time }) {
Block { Time }
Trade {
Dex { ProtocolName }
Buy { AmountInUSD Currency { Symbol } }
Sell { AmountInUSD Currency { Symbol } }
}
Transaction { Hash }
}
}
}