Getting started with the API

Once you have an API key (see creating your first API key), every request authenticates with the nodeUrlOrApiAccessKey header — your API key as a raw value, no Bearer prefix.

A typical first sequence

1. GET /api/Blocks/blockchain-info — confirms your key and connection work
2. POST /api/Wallet/create with {"walletName": "..."} — creates your identity anchor
3. POST /api/Address/create (needs the walletName and an encryptedPassphrase header) — generates an address under that wallet
4. GET /api/Address/address-balance — checks a balance

Signing and verifying messages — the mechanism behind authentication and authorization — are their own endpoints: /api/Address/sign-message and /api/Address/verify-message.

Response format

Every response is wrapped as { successful, message, data }. Importantly, a failed operation can still come back as HTTP 200 with successful: false — always check that field, not just the HTTP status code. See common API errors for the specifics.

Base URL

Use the base URL shown in your own dashboard/API reference for your account and plan — it can vary (Enterprise plans use a dedicated node URL instead of the shared endpoint).