Overview

Create an account, mint an API key, and send your first telemetered transaction — a self-serve walkthrough of the 0block dashboard.

Beta — rolling out now. The dashboard and its control-plane API are in active rollout. The contract documented here is stable, but availability may vary by deployment.

The 0block dashboard is a self-serve control plane: create an account, mint and revoke API keys, and review per-transaction telemetry with landing detection. Everything the UI does is backed by a REST API under /api/v1 that you can call directly.

Base URL: your gateway origin (for example https://nyc.0block.io), with all routes under /api/v1.
Content type: JSON in and out; timestamps are ISO-8601 UTC.
Session auth: Authorization: Bearer <session token>.
Errors: { "error": { "code": "<machine_code>", "message": "<human>" } } with a matching HTTP status.

Walkthrough

This is the fastest path from zero to a telemetered submission.

Create your account

Sign up in the 0block dashboard. Accounts are created in the dashboard web UI — there is no signup API to call. See Authentication for how the dashboard manages your session.

Create an API key

In the dashboard, open API Keys and create one. The full key is shown once at creation — copy it immediately; after that only its 0b_ + 8-character prefix is ever shown again. The Keys API reference documents the endpoint the dashboard calls on your behalf.

Submit a transaction with the key

Pass the key as X-API-Key. Submissions authenticated with a key are telemetered so you can track them later.

curl -s -X POST 'https://nyc.0block.io/' \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: <YOUR_API_KEY>' \
  -d '{"jsonrpc":"2.0","id":1,"method":"sendTransaction","params":["<base64-tx>",{"encoding":"base64"}]}'

See Send Transaction for the full submission contract.

Read it back

Watch each submission move through its landing lifecycle in the dashboard's Transactions view. The same history and stats are available from the control-plane API — see the Transactions & Stats reference — authorized with the session token from your dashboard sign-in.

See Tracking your transactions for the status lifecycle.

Where to go next

Authentication — sessions vs. API keys, and how each is used.
Tracking your transactions — the received → forwarded → acked → landed/reverted lifecycle, slot_delta, and landing_ms.
API Reference — Auth, API Keys, Transactions & Stats.