Wallet Infrastructure API

Download the Postman collection and OpenAPI 3.0 specification for the Bitnob Wallet Infrastructure (Enterprise) API — non-custodial wallets, transactions, gas stations, on-chain subscriptions, and platform webhooks across multiple chains.

Both artifacts are generated from the same canonical spec and stay in sync; pick the one that fits your workflow.

Authentication

The Wallet Infrastructure API authenticates with an X-API-Key header (one secret per organization, scoped permissions) — not the HMAC signing flow used by the rest of the Bitnob API. Paste your key into the Postman environment's api_key variable, or set it as the X-API-Key header when calling the spec from any other tool.

Postman Collections

Collection File

Complete API collection with all endpoints, examples, and tests

Environment File

Pre-configured environment variables for sandbox and production

Setup Instructions

Download Collection

Download the Postman collection file containing all API endpoints

Import to Postman

Open Postman → Import → Select the downloaded JSON file

Set Environment

Download and import the environment file with pre-configured variables

Configure API Key

Set your API key in the environment variables

Environment Variables

Variables in the environment file

base_url — defaults to https://api.platform.bitnob.com

api_key — paste your X-API-Key here (stored as a secret, masked in the UI)

What's in the collection

Wallets — list / get / create wallets, update metadata, list balances, derive and list addresses

Vaults — list and get vaults (HD seed containers)

Transactions — list, get, and create signed transactions; filter by wallet, status, direction, asset, date range

Gas Stations — create, list, get, update; refill from a wallet; sponsor and broadcast external Tron transactions

Subscriptions — manage on-chain address subscriptions, inspect delivery events, retry failures, rotate signing secrets

Webhooks — manage platform notification webhooks and their delivery history

Assets — list supported assets and chains

RPC — proxy JSON-RPC 2.0 calls to supported blockchain nodes

Meta — GET /me for API key info and permissions

OpenAPI Specification

The canonical OpenAPI 3.0 spec — feed it straight into openapi-generator, Prism, Spectral, Stoplight, Insomnia, or import it into Postman if you'd rather not use the pre-built collection.

Specification files

bitnob-wallet-infrastructure.openapi.json

OpenAPI 3.0 spec in JSON — best for code generators and tooling

bitnob-wallet-infrastructure.openapi.yaml

Same spec in YAML — easier to read, review, and diff in pull requests

What's covered

30 paths · 42 operations across 9 resource tags

30 reusable schemas for request bodies and response objects

Idempotency, pagination, rate-limit, and error envelopes all documented inline so generated clients handle them correctly out of the box

Webhook signature verification (HMAC-SHA256 over the canonical {data, event, timestamp} object) and the full event-type catalogue

Quick Start

Postman

Click Download Collection above and import the JSON into Postman

Click Download Environment and import it as a new environment

Open the environment, paste your X-API-Key into the api_key variable, and save

Pick Meta → Get API key info and hit Send — a 200 OK echoing back your organization confirms everything is wired up

openapi-generator (any language)

openapi-generator-cli generate \
  -i https://docs.bitnob.com/api-collections/swagger/bitnob-wallet-infrastructure.openapi.json \
  -g typescript-fetch \
  -o ./bitnob-wallet-client

curl

curl https://api.platform.bitnob.com/me \
  -H "X-API-Key: $BITNOB_API_KEY"

Security

X-API-Key is a credential — never commit it to source control or expose it in a browser/mobile client. Keep sandbox and production keys in separate Postman environments so you can't accidentally hit production with a sandbox key (or vice versa).