Actions20
- Bridge Actions
- Category Actions
- Chain Actions
- DEXs & Volume Actions
- Fees & Revenue Actions
- Hack Actions
- Oracle Actions
- Protocol Actions
- Raise Actions
- Stablecoin Actions
- TVL Actions
- Yield Actions
Overview
The node integrates with the DefiLlama API to retrieve volume data for a specific cross-chain bridge. It fetches historical and aggregated volume metrics over selectable time ranges (24 hours, 7 days, or 30 days). This is useful for monitoring the activity and liquidity flow through bridges connecting different blockchain networks.
Typical use cases include:
- Tracking the transaction volume of a particular bridge to analyze its usage trends.
- Comparing volumes across multiple bridges for DeFi analytics or reporting.
- Feeding bridge volume data into dashboards or alerting systems.
For example, you can get the 7-day volume of the Polygon PoS Bridge by specifying its bridge ID and selecting the 7-day date range.
Properties
| Name | Meaning |
|---|---|
| Bridge ID | The identifier of the bridge to query (e.g., "1" for Polygon PoS Bridge). |
| Additional Fields | A collection of optional parameters: |
| - Max Results | Maximum number of results to return (1-100). Not typically used for this operation. |
| - Date Range | Time range for data aggregation; options are "24 Hours", "7 Days", or "30 Days". |
| - Min Volume | Minimum volume threshold in USD to filter results (not applicable here since single bridge). |
Output
The output JSON contains detailed volume data for the specified bridge, including:
volume: The total volume for the selected date range.volumeHistory: An array of historical volume entries with timestamps filtered according to the chosen date range.dateRange: The selected time range string ("24h", "7d", or "30d").- Other metadata fields related to the bridge's volume statistics.
If AI Agent Mode is enabled, the output will be simplified and structured with an additional human-readable summary describing the volume data.
Dependencies
- Requires access to the DefiLlama Bridges API endpoint at
https://bridges.llama.fi/bridgevolume/{bridgeId}. - Optionally uses an API key credential if provided, sent as a Bearer token in the Authorization header.
- No other external dependencies beyond standard HTTP requests via axios.
Troubleshooting
- Missing or invalid Bridge ID: The Bridge ID parameter is required. Ensure it is correctly set and corresponds to a valid bridge on DefiLlama.
- API errors (400 or 404): These indicate invalid bridge IDs or that the bridge does not exist. Verify the bridge ID and try again.
- Empty or no data returned: Could be due to no volume data available for the selected date range or bridge. Try adjusting the date range or checking bridge status.
- Rate limiting or network issues: If requests fail repeatedly, check network connectivity and API rate limits.