Crossmint icon

Crossmint

Hybrid integration: transfer money using Crossmint with external wallet support

Actions7

Overview

The "Get Wallet" operation of the Crossmint node retrieves detailed information about a blockchain wallet using various locator types. This node is useful when you need to fetch wallet data based on different identifiers such as wallet address, email, user ID, phone number, or social media handles (Twitter or X). It supports multiple blockchain types including Ethereum Virtual Machine (EVM) and Solana.

Typical use cases include:

  • Retrieving wallet details for a user identified by their email or social handle.
  • Fetching wallet information directly by its blockchain address.
  • Integrating with systems that manage wallets across different blockchains and user identifiers.

For example, you can get the wallet info of a user by specifying their Twitter handle and chain type, or directly query a wallet by its blockchain address.

Properties

Name Meaning
Locator Type The method used to identify the wallet. Options: Wallet Address, Email, User ID, Phone Number, Twitter Handle, X Handle.
Wallet Address The blockchain wallet 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 Locator Type is not "Wallet Address". Options: EVM (Ethereum Virtual Machine), Solana.

Output

The output JSON contains the wallet information retrieved from the Crossmint API. The structure depends on the API response but generally includes:

  • Wallet metadata such as wallet type, chain type, and configuration.
  • Owner information if available.
  • Addresses and public keys related to the wallet.
  • Additional wallet-specific details as returned by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to 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 other external dependencies are required.

Troubleshooting

  • Missing Required Fields: If a required property for the selected locator type is missing or empty, the node throws an error indicating which field is required.
  • Unsupported Locator Type: Using a locator type outside the supported list will cause an error.
  • API Request Failures: Network issues or invalid API keys will result in API errors. Ensure the API key is valid and the endpoint is reachable.
  • Invalid Input Format: For example, an improperly formatted email or wallet address may cause errors.
  • To resolve errors, verify all required inputs are correctly provided and the API key credential is properly configured.

Links and References

Discussion