Actions6
- Wallet Actions
- Checkout Actions
Overview
This node allows you to retrieve the balance of a blockchain wallet using various types of wallet locators. It supports querying balances on multiple blockchain chains and for multiple tokens simultaneously. This is useful in scenarios where you need to monitor or report the token holdings of wallets identified by different user identifiers (e.g., email, phone number) or directly by wallet address.
Practical examples include:
- Checking the ETH and USDC balances of a user's wallet identified by their email on Ethereum and Polygon chains.
- Retrieving token balances for a wallet identified by a Twitter handle on Solana.
- Monitoring your own wallet balance ("me" locator) across several chains and tokens.
Properties
| Name | Meaning |
|---|---|
| Locator Type | Type of wallet locator to use. Options: Wallet Address, Email, User ID, Phone Number, Twitter Handle, X Handle, Me (the authenticated user's wallet). |
| Wallet Address | The wallet address to query (required if Locator Type is "Wallet Address"). Example: 0x1234567890123456789012345678901234567890. |
| Email address of the wallet owner (required if Locator Type is "Email"). | |
| User ID | User ID of the wallet owner (required if Locator Type is "User ID"). |
| Phone Number | Phone number of the wallet owner with country code (required if Locator Type is "Phone Number"). |
| Twitter Handle | Twitter handle of the wallet owner without '@' (required if Locator Type is "Twitter Handle"). |
| X Handle | X handle of the wallet owner without '@' (required if Locator Type is "X Handle"). |
| Chain Type | Blockchain type for the wallet locator (required if Locator Type is not "Wallet Address"). Options: EVM (Ethereum Virtual Machine), Solana. |
| Chains | Comma-separated list of blockchain chains to query balances from. Examples: ethereum, polygon, ethereum-sepolia. |
| Tokens | Comma-separated list of tokens to query balances for. Examples: eth, usdc, usdt. |
Output
The output JSON contains the balance information retrieved from the Crossmint API for the specified wallet locator, chains, and tokens. The structure typically includes:
- Wallet identifier used for the query.
- Balances per chain and per token, including amounts available.
- Metadata about the queried wallet and tokens.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for the Crossmint service.
- The node makes HTTP requests to the Crossmint API endpoints, either production or staging based on the configured environment in credentials.
- No additional external dependencies are required.
Troubleshooting
- Missing Required Fields: If a required property for the selected locator type is missing or empty (e.g., wallet address when Locator Type is "Wallet Address"), the node throws an error indicating which field is required.
- Invalid Locator Type: Using an unsupported locator type will cause an error.
- API Errors: Network issues or invalid API keys will result in API errors returned by the Crossmint service.
- Incorrect Chains or Tokens Format: Chains and tokens must be comma-separated strings; incorrect formatting may lead to unexpected results or errors.
- Empty or Invalid Token Amounts: Although not applicable here (balance retrieval), ensure tokens are valid symbols recognized by the API.
To resolve errors:
- Verify all required input fields are correctly filled.
- Check that the API key credential is valid and has appropriate permissions.
- Confirm the chains and tokens strings are properly formatted.
- Review error messages for specific missing or invalid parameters.
Links and References
- Crossmint API Documentation (for detailed API usage and supported chains/tokens)
- Ethereum Virtual Machine (EVM)
- Solana Blockchain
This summary is based solely on static analysis of the provided source code and property definitions.