Addresses
Blockchain addresses are unique identifiers used to send and receive digital assets. This section allows you to manage, generate, and validate addresses associated with customers.
GET addresses
Use Case
This endpoint returns a paginated list of wallet addresses associated with users or companies. Commonly used for auditing address activity or linking addresses to accounts.
Address Sample Response
Unique identifier of the address. This is a UUID assigned when the address is created.
The actual blockchain address generated by the system, used to receive or send cryptocurrency.
The unique identifier of the company that owns or manages this address.
A user-defined name or label for easy identification of the address. Often used to differentiate between purposes (e.g., 'Primary Deposit Address').
The blockchain network the address is associated with (e.g., 'bitcoin', 'ethereum', 'bsc'). Determines how transactions are routed.
The current status of the address. Typically 'active' for addresses that can receive deposits, or 'inactive' for disabled addresses.
Timestamp indicating when the address was created.
A client-provided reference string for tracking purposes. May be empty if not provided during address creation.
Cursor token for fetching the next page of results. Empty string when there are no more pages.
Indicates whether there are more results available beyond the current page.
Query Parameters
Filter and paginate the address list with any combination of these parameters on GET /api/addresses. Pagination is cursor-based — pass data.next_cursor from the previous response to fetch the next page.
Filter by blockchain network (e.g. 'bitcoin', 'ethereum', 'bsc', 'polygon', 'solana', 'tron', 'stellar', 'avalanche').
Filter by address status — 'active' for usable addresses, 'inactive' for disabled ones.
Filter by one or more blockchain address strings. Useful for looking up a specific address without its UUID.
Opaque base64 pagination cursor. Pass data.next_cursor from the previous response to fetch the next page. Omit on the first request.
Maximum number of records to return per page. Default is 20.
Get Address by ID or Address
Use Case
Retrieve a single address using its unique UUID or address string. Useful for looking up detailed address activity or metadata.
The unique identifier for the address, usually auto-generated by the system. It can be used to fetch specific address details or manage address lifecycle events.
The actual blockchain address to query. This is the alphanumeric string used for sending or receiving crypto assets on a specific chain, such as Bitcoin or Ethereum.
Get Address by ID or Address Sample Response
Unique identifier assigned to the address.
The blockchain address string used to receive funds.
Identifier of the company this address belongs to.
Human-readable label for the address (e.g. 'bsc Test', 'test-address').
Blockchain network the address belongs to (e.g. 'bitcoin', 'ethereum', 'avalanche').
Current status of the address: 'active' or 'inactive'.
RFC 3339 / ISO 8601 timestamp of when the address was created (UTC).
Generate Addresses
Use Case
Generate or assign a new address for a supported blockchain, optionally tied to a customer.
Generate Addresses Sample Request
Blockchain network to generate the deposit address on. Determines the address format. Supported values: 'bitcoin', 'ethereum', 'bsc', 'polygon', 'solana', 'tron', 'stellar'.
Email of the customer this address belongs to. Must match a customer already registered via the Customers API. Links incoming deposits to that customer for attribution.
Human-readable label to help you identify this address (e.g. 'test-address', 'hot-wallet-1').
Client-generated unique identifier for this address request. Returned on the response and useful for idempotency and internal tracking.
Generate Addresses Sample Response
Unique identifier assigned to the generated address.
The blockchain network the address belongs to (e.g., 'bitcoin', 'ethereum').
UUID of the company that owns the address.
The generated blockchain address.
Current status of the address (e.g., 'active').
A user-friendly name to identify the address (e.g., 'Primary Deposit Address').
Client-provided reference string for tracking purposes.
Stellar Address Generation
On Stellar, Bitnob does not mint a fresh blockchain address each time you call POST /api/addresses with chain: "stellar". Every request for your company returns the same single shared Stellar wallet address, because all Stellar deposits land on one account and are attributed downstream via memos.
If you need to distinguish deposits per user, generating the address is not enough — you must also assign and surface a unique memo to each end-user. Bitnob does not generate or manage memos on your behalf.
Validate Address
Use Case
Validates whether an address is well-formed and supported on a given chain. Does not assign or persist the address — only validates its format.
Validate Address Sample Request
The blockchain address you want to validate. It should be in the correct format for the selected chain (e.g., a Bitcoin address like 'bc1q...').
The blockchain network the address belongs to (e.g., 'bitcoin', 'ethereum'). This helps ensure the address is valid for the correct network.
Validate Address Response
Indicates whether the API request was processed successfully.
A human-readable message describing the result of the validation operation.
Returns true if the provided blockchain address is valid for the specified chain, otherwise false.
The blockchain address that was validated.
The blockchain network the address was validated against (e.g., 'solana', 'ethereum').
A unique identifier for this specific API request, useful for debugging and support.
The UTC timestamp when the validation was completed.
Stablecoins Supported Chains
Use Case
Displays all supported blockchain networks along with their native tokens and stablecoins.
Helps developers identify which tokens can be used for transactions and ensures correct decimals are applied when sending or receiving assets.
Live supports more chains than sandbox. Production currently returns 13 chains; sandbox returns a subset of those — every chain in the sandbox list is fully usable for testing. Call this endpoint from the environment you plan to use to get its authoritative list before integrating a new chain.
Stablecoins Supported Chains Response
A list of supported blockchain networks, each containing its native token and available stablecoins.
The name of the blockchain network (e.g., 'arbitrum', 'bsc', 'ethereum', 'tron').
Details of the chain's native token, including symbol and decimals.
A list of stablecoins supported on the chain, each with symbol and decimals.
The symbol of the chain's native token (e.g., 'ETH', 'BNB', 'TRX').
The number of decimals used by the native token.