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.

Address API Endpoints

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.

Base URL

Address Sample Response
1
idstring (UUID)

Unique identifier of the address. This is a UUID assigned when the address is created.

2
addressstring

The actual blockchain address generated by the system, used to receive or send cryptocurrency.

3
company_idstring (UUID)

The unique identifier of the company that owns or manages this address.

4
labelstring

A user-defined name or label for easy identification of the address. Often used to differentiate between purposes (e.g., 'Primary Deposit Address').

5
chainstring

The blockchain network the address is associated with (e.g., 'bitcoin', 'ethereum', 'bsc'). Determines how transactions are routed.

6
statusstring

The current status of the address. Typically 'active' for addresses that can receive deposits, or 'inactive' for disabled addresses.

7
created_atstring (ISO 8601)

Timestamp indicating when the address was created.

8
referencestring

A client-provided reference string for tracking purposes. May be empty if not provided during address creation.

9
next_cursorstring

Cursor token for fetching the next page of results. Empty string when there are no more pages.

10
has_moreboolean

Indicates whether there are more results available beyond the current page.

Address Sample Response

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.

1
chainstringOptional

Filter by blockchain network (e.g. 'bitcoin', 'ethereum', 'bsc', 'polygon', 'solana', 'tron', 'stellar', 'avalanche').

2
statusstringOptional

Filter by address status — 'active' for usable addresses, 'inactive' for disabled ones.

3
addressesstringOptional

Filter by one or more blockchain address strings. Useful for looking up a specific address without its UUID.

4
cursorstringOptional

Opaque base64 pagination cursor. Pass data.next_cursor from the previous response to fetch the next page. Omit on the first request.

5
limitnumberOptional

Maximum number of records to return per page. Default is 20.

Sample Requests

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.

1
idString (UUID)Yes

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.

2
addressStringYes

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

Get Address by ID or Address Sample Response
1
idUUID

Unique identifier assigned to the address.

2
addressString

The blockchain address string used to receive funds.

3
company_idUUID

Identifier of the company this address belongs to.

4
labelString

Human-readable label for the address (e.g. 'bsc Test', 'test-address').

5
chainString

Blockchain network the address belongs to (e.g. 'bitcoin', 'ethereum', 'avalanche').

6
statusString

Current status of the address: 'active' or 'inactive'.

7
created_atDate

RFC 3339 / ISO 8601 timestamp of when the address was created (UTC).

Address Response Sample

Generate Addresses

Use Case

Generate or assign a new address for a supported blockchain, optionally tied to a customer.

Base URL

Generate Addresses Sample Request
1
chainstringRequired

Blockchain network to generate the deposit address on. Determines the address format. Supported values: 'bitcoin', 'ethereum', 'bsc', 'polygon', 'solana', 'tron', 'stellar'.

2
customer_emailstringOptional

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.

3
labelstringOptional

Human-readable label to help you identify this address (e.g. 'test-address', 'hot-wallet-1').

4
referencestringOptional

Client-generated unique identifier for this address request. Returned on the response and useful for idempotency and internal tracking.

Sample Request

Generate Addresses Sample Response
1
idstring (UUID)

Unique identifier assigned to the generated address.

2
chainstring

The blockchain network the address belongs to (e.g., 'bitcoin', 'ethereum').

3
company_idstring (UUID)

UUID of the company that owns the address.

4
addressstring

The generated blockchain address.

5
statusstring

Current status of the address (e.g., 'active').

6
labelstring

A user-friendly name to identify the address (e.g., 'Primary Deposit Address').

7
referencestring

Client-provided reference string for tracking purposes.

Sample Response

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.

What This Means for You

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.

Stellar Address Generation

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 - Request

Validate Address Sample Request
1
addressStringRequired

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...').

2
chainStringRequired

The blockchain network the address belongs to (e.g., 'bitcoin', 'ethereum'). This helps ensure the address is valid for the correct network.

Sample Request

Validate Address Response
1
successboolean

Indicates whether the API request was processed successfully.

2
messagestring

A human-readable message describing the result of the validation operation.

3
validboolean

Returns true if the provided blockchain address is valid for the specified chain, otherwise false.

4
addressstring

The blockchain address that was validated.

5
chainstring

The blockchain network the address was validated against (e.g., 'solana', 'ethereum').

6
request_idstring

A unique identifier for this specific API request, useful for debugging and support.

7
timestampstring (ISO 8601)

The UTC timestamp when the validation was completed.

Response

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.

Sandbox vs. Live Coverage

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.

Endpoint

Stablecoins Supported Chains Response
1
chainsarray

A list of supported blockchain networks, each containing its native token and available stablecoins.

2
chainstring

The name of the blockchain network (e.g., 'arbitrum', 'bsc', 'ethereum', 'tron').

3
nativeTokenobject

Details of the chain's native token, including symbol and decimals.

4
stablecoinsarray

A list of stablecoins supported on the chain, each with symbol and decimals.

5
symbolstring

The symbol of the chain's native token (e.g., 'ETH', 'BNB', 'TRX').

6
decimalsnumber

The number of decimals used by the native token.

Sample Response

Did you find this page useful?