Soroswap icon

Soroswap

Interact with Soroswap DEX on Stellar network

Actions12

Overview

This node integrates with the Soroswap decentralized exchange (DEX) on the Stellar network, enabling users to interact programmatically with various Soroswap features. The "Get User Positions" operation specifically retrieves liquidity positions held by a user in Soroswap pools.

Typical use cases include:

  • Portfolio tracking: Fetching a user's current liquidity pool positions to monitor their DeFi investments.
  • Analytics dashboards: Displaying user-specific liquidity data within custom applications or reports.
  • Automated DeFi management: Triggering workflows based on user liquidity status, such as rebalancing or withdrawing liquidity.

For example, a user can input their wallet address and select the network (Mainnet or Testnet) to obtain detailed information about all liquidity positions they hold on Soroswap.

Properties

Name Meaning
Network Selects the blockchain network to operate on. Options: Mainnet, Testnet
User Address The wallet address of the user whose liquidity positions are to be retrieved (required)

Output

The output is a JSON object containing the user's liquidity positions on Soroswap for the specified network. This typically includes details such as the pools the user has provided liquidity to, amounts of tokens supplied, and possibly metadata about each position.

The node does not output binary data.

Example output structure (simplified):

{
  "positions": [
    {
      "poolId": "string",
      "assetA": "string",
      "assetB": "string",
      "liquidityAmount": "string",
      "otherDetails": { /* additional position info */ }
    },
    ...
  ]
}

Dependencies

  • Requires an API key credential for Soroswap's SDK service.
  • Uses the Soroswap SDK library to communicate with Soroswap endpoints.
  • Needs network selection (Mainnet or Testnet) to target the correct environment.

Troubleshooting

  • Invalid or missing user address: Ensure the wallet address is correctly formatted and provided; otherwise, the node will fail to fetch positions.
  • API key issues: If authentication fails, verify that the API key credential is valid and has necessary permissions.
  • Network mismatch: Selecting the wrong network (e.g., Testnet instead of Mainnet) may result in empty or unexpected results.
  • Unknown operation error: This node supports specific operations; ensure "Get User Positions" is selected when using this functionality.
  • Rate limits or connectivity problems: Network or API rate limiting issues may cause errors; retry or check network connectivity.

Links and References

Discussion