Actions6
- Wallet Actions
- Checkout Actions
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 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 info directly by its blockchain address.
- Accessing the wallet associated with the API client ("me") for authenticated operations.
For example, you can get the wallet info of a user by specifying their email and chain type, or directly query a wallet by its blockchain address.
Properties
| Name | Meaning |
|---|---|
| Locator Type | Type of wallet locator to use. Options: Wallet Address, Email, User ID, Phone Number, Twitter Handle, X Handle, Me (client API key) |
| Wallet Address | The blockchain wallet address (required if Locator Type is Wallet Address) |
| 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. Options: EVM (Ethereum Virtual Machine), Solana (required for all locator types except Wallet Address) |
Output
The output JSON contains the wallet information retrieved from the Crossmint API. This typically includes wallet metadata such as wallet ID, address, owner information, chain type, and configuration details.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Crossmint API.
- The node uses the Crossmint API endpoints, switching between staging and production environments based on the credential's environment setting.
- No additional external dependencies are required beyond the configured API key.
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. Ensure all mandatory fields are filled.
- Unsupported Locator Type: Using a locator type not supported by the node will result in an error. Use only the provided locator options.
- Invalid API Key or Network Issues: API request failures may occur due to invalid credentials or network problems. Verify the API key and network connectivity.
- Empty or Malformed Input: Providing empty strings or malformed inputs (e.g., invalid email format) will cause errors. Validate inputs before execution.
Links and References
This summary covers the static analysis of the "Get Wallet" operation within the Crossmint node implementation, focusing on input properties, output structure, dependencies, and common troubleshooting points.