Actions12
Overview
This node integrates with the Soroswap decentralized exchange (DEX) on the Stellar network, enabling users to interact programmatically with various liquidity and trading features. It supports multiple operations such as retrieving pools, getting trading quotes, adding/removing liquidity, and more.
The Get Pools operation specifically fetches liquidity pools available on selected protocols within the Soroswap ecosystem for a given network (Mainnet or Testnet). This is useful for traders, liquidity providers, or analytics tools that need up-to-date information about available pools across different protocols.
Practical examples:
- A DeFi dashboard fetching all active liquidity pools on Soroswap and related protocols to display pool statistics.
- Automated trading bots querying pools to find arbitrage opportunities.
- Portfolio management tools retrieving pools to analyze liquidity distribution.
Properties
| Name | Meaning |
|---|---|
| Network | The blockchain network to use for the operation. Options: Mainnet, Testnet. |
| Protocols | One or more protocols to query pools from. Options: Soroswap, Phoenix, Aqua, SDEX. |
Output
The output JSON contains an array of pool objects retrieved from the specified protocols on the chosen network. Each pool object typically includes details such as token pairs, liquidity amounts, fees, and other metadata relevant to the liquidity pool.
The exact structure depends on the external SDK response but generally provides comprehensive data about each pool's state.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Soroswap SDK service.
- Uses the Soroswap SDK (
@soroswap/sdk) internally to communicate with the Soroswap API endpoints. - Needs proper configuration of the API key and optionally a base URL for the Soroswap API in the node credentials.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Selecting unsupported or misspelled protocol names may result in empty or error responses.
- Network selection mismatch (e.g., using Mainnet keys on Testnet) can lead to no data or errors.
Error messages:
"Unknown operation: getPools"— indicates the operation parameter was not set correctly; ensure "Get Pools" is selected.- API errors returned from the Soroswap service will be included in the node output if "Continue On Fail" is enabled.
Resolutions:
- Verify API key validity and permissions.
- Confirm correct network and protocol selections.
- Enable "Continue On Fail" to handle partial failures gracefully during batch executions.
Links and References
- Soroswap Official Website
- Stellar Network Documentation
- Soroswap SDK GitHub Repository (for detailed API and usage)