get
https://public-api.birdeye.so/defi/txs/pair
Retrieve a list of trades of a specified pair.
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
Legacy trade list for one pair or pool.
- Pass the pair address in
address. limitsupports1to50items per request, andoffsetsupports up to50,000.tx_typedefaults toswapand can also be used to inspectaddorremoveliquidity events.- Pair-level trade history is useful when venue-specific behavior matters more than token-level aggregation.
- Use descending sort when you want the most recent trades first.
- Standard
- Lite
- Starter
- Premium
- Business
- Enterprise
All chains ⛓️ ✨
Compute Unit ⚙️
- This endpoint consumes
10 CUper request.
Use Cases 💡
- Inspect venue-specific trade flow for one pool or pair.
- Monitor pair activity for LP analysis, execution review, or routing research.
- Compare one pair's tape with token-level aggregates to spot fragmented liquidity behavior.
- Build pair trade feeds for dashboards or trading surfaces.
How to Use 🛠️
- Set
x-chainfor the target network. - Pass the pair address in
address. - Page with
offsetandlimit, keepinglimitat50or below. - Use
tx_typeto isolate swaps versus liquidity changes.
Best Practices ✅
- Prefer pair-level trades when the asset has multiple active venues and you care about one exact market.
- Keep pair identity visible in your UI so the feed is not confused with token-wide trading.
- Pair this endpoint with pair OHLCV and liquidity endpoints for fuller venue diagnostics.