Crossmint icon

Crossmint

Hybrid integration: transfer money using Crossmint with external wallet support

Actions7

Overview

This node integrates with the Crossmint API to retrieve the balance of a specified wallet on supported blockchains. It supports multiple ways to identify the wallet owner, including direct wallet address or user identifiers such as email, user ID, phone number, Twitter handle, or X handle. The node queries balances for specified blockchain chains and tokens.

Common scenarios include:

  • Checking the token balances of a user's wallet by their email or social handles.
  • Monitoring balances across multiple blockchain networks and tokens.
  • Integrating wallet balance checks into automated workflows for finance, reporting, or alerting.

Example: Retrieve the ETH and USDC balances of a wallet identified by an email address on the Ethereum Sepolia testnet.

Properties

Name Meaning
Locator Type Type of wallet locator to use. Options: Wallet Address, Email, User ID, Phone Number, Twitter Handle, X Handle.
Wallet Address The wallet's blockchain address (required if Locator Type is "Wallet Address").
Email 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 when using Email, User ID, Phone Number, Twitter, or X. Options: EVM (Ethereum Virtual Machine), Solana. Required for these locator types.
Chains Comma-separated list of blockchain chains to query balances from (e.g., ethereum-sepolia, polygon). Required.
Tokens Comma-separated list of tokens to query balances for (e.g., eth, usdc, usdt). Required.

Output

The output JSON contains the balance information retrieved from the Crossmint API for the specified wallet and tokens on the requested chains.

Typical structure includes:

  • Token balances per chain.
  • Metadata about the wallet and queried tokens.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for the Crossmint API.
  • The node makes HTTP requests to either the production or staging Crossmint API endpoints depending on the configured environment in credentials.
  • No additional external libraries are required beyond those bundled (ethers.js, solana/web3.js, bs58) which are used internally for other operations but not directly for balance retrieval.

Troubleshooting

  • Missing Required Fields: If required fields like wallet address or email are missing based on the locator type, the node throws errors 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.
  • Empty or Malformed Chains/Tokens: Ensure that the chains and tokens parameters are correctly formatted comma-separated strings.
  • Chain Type Requirement: For locator types other than wallet address, specifying the correct chain type (EVM or Solana) is mandatory.

To resolve errors:

  • Verify all required input properties are provided and valid.
  • Check API key validity and permissions.
  • Confirm network connectivity to the Crossmint API endpoint.
  • Use correct formatting for chains and tokens.

Links and References

Discussion