When to Use
- You need post-trade analytics - reconciling fills, tracking volumes, or attributing trades to your integration via the
sourceparameter - You want to inspect any Bebop transaction across all supported chains from a single endpoint, without querying each chain separately
At a Glance
| Transport | REST |
| Authentication | Optional (required only for source filtering) |
| Base URL | https://api.bebop.xyz/history/v2/ |
| Complexity | Low - standard REST GET requests |
How It Works
| Step | Action | You send | You get back |
|---|---|---|---|
| 1 | Query trades | Wallet address → GET /history/v2/trades | Paginated list of trades with token + USD details |
| 2 | Inspect a transaction | Tx hash → GET /history/v2/tx/{tx_hash} | Full trade breakdown: tokens, amounts, gas, type |
source (partner attribution), authenticate with your API key.
Key Endpoints
| Endpoint | Purpose |
|---|---|
GET /history/v2/trades | Query trades by wallet address with time range and pagination |
GET /history/v2/tx/{tx_hash} | Look up a specific transaction by hash |
Next Steps
Quickstart
Fetch your first trade history in a few minutes.