Use this endpoint to register a customer’s existing blockchain wallet address with SpherePay. SpherePay does not create or custody wallets — it links an address your customer already owns to their SpherePay profile so that transfers can be routed to or from that address. You must register at least one wallet before creating a transfer that involves crypto. The wallet address must already exist on the target network before registration.Documentation Index
Fetch the complete documentation index at: https://docs.spherepay.co/llms.txt
Use this file to discover all available pages before exploring further.
Endpoint
Authentication
All requests require a Bearer token in theAuthorization header.
Request parameters
The unique identifier of the customer who owns this wallet.
The wallet address on the specified network. Must be a valid address format for the chosen network (e.g., a 44-character base58 string for Solana, or a
0x-prefixed 42-character hex string for EVM networks).The blockchain network for this wallet. Must be one of:
| Value | Network |
|---|---|
"sol" | Solana |
"ethereum" | Ethereum |
"polygon" | Polygon |
"base" | Base |
"arbitrum" | Arbitrum |
"avalanche" | Avalanche |
"tron" | Tron |
"starknet" | Starknet |
Response fields
Unique identifier for the registered wallet. Store this value and use it in transfer requests.
The blockchain address that was registered.
The network code this wallet is registered on (e.g.,
"sol", "ethereum").ID of the customer who owns this wallet.
ISO 8601 timestamp of when the wallet was registered.
ISO 8601 timestamp of the most recent update.
Error responses
| Status | Code | Description |
|---|---|---|
400 | address/invalid | The wallet address is invalid for the specified network. |
404 | resource/not-found | The specified customer ID does not exist. |
422 | validation/failed | Validation failed. The response includes a per-field errors array. |

