Overview
Read-only reference data for every asset and chain Bitnob Enterprise supports. Use these endpoints to populate asset pickers, resolve an asset_id to its chain and decimals, or discover which networks are available before deriving an address. All routes require an API key with read access.
List Assets
Use Case
Returns all supported assets. Filter by chain, network, or type to narrow the list to the assets relevant to your integration.
Query Parameters
Filter to a single blockchain (e.g. `ethereum`, `bitcoin`, `tron`, `solana`).
Filter to a single network within the chain (e.g. `mainnet`, `sepolia`).
Filter by asset type: `native` for the chain's gas asset, `token` for contract-issued assets.
Asset Fields
Always `asset`. Identifies the record type.
Stable identifier for the asset. Pass it as `asset_id` when deriving addresses or creating transactions.
Human-readable asset name (e.g. `USD Coin`, `Ether`).
Ticker symbol (e.g. `USDC`, `ETH`, `BTC`).
Blockchain the asset lives on.
`native` for the chain's gas asset; `token` for ERC-20s, SPLs, TRC-20s, and similar.
Number of decimal places the asset uses. Use it to convert between raw and human-readable amounts.
List Chains
Use Case
Returns every blockchain network Bitnob Enterprise serves, with the list of networks available on each chain.
Chain Fields
Always `chain`.
Chain identifier (e.g. `ethereum`, `bitcoin`, `tron`). Use this value wherever a `chain` is expected.
Display-friendly chain name (e.g. `Ethereum`, `Tron`).
Networks available on the chain (e.g. `mainnet`, `sepolia`, `testnet`).
Get Asset
Use Case
Returns a single asset by ID.
Path Parameters
The asset's unique identifier.
The response is a single asset object — the same field shape as each entry in List Assets. Returns 404 if the asset is not supported.