​

Developers

import { BlankClient } from "@blankdotbuild/sdk";

const blank = new BlankClient({ apiKey: process.env.BLANK_API_KEY });

const token = await blank.tokens.get(mintAddress);
console.log(token.data.symbol, token.metadata.requestId);

​

What the API covers

​

What the API does not cover

• Programmatic token launches. Tokens are launched from blank.build.
• Buying, selling, staking, unstaking, or claiming. Those are wallet-signed app and dashboard flows.
• Enabling or changing fee allocations, staking allocations, or Price Prediction allocations.
• Audience exports.
• Any unversioned Worker path. Paths outside /api/v2 are internal and carry no stability contract.

​

Design contract

• Environment-bound keys. A key belongs to one Blank account, one environment, and that account’s single verified wallet. See Authentication.
• Least-privilege scopes. Every protected operation declares the scopes it requires. See Scopes.
• RFC 9457 Problem Details. Every error is application/problem+json with a stable code and a requestId. See Errors.
• Durable idempotency. Every mutation requires an Idempotency-Key and is committed atomically. See Conventions.
• Cursor pagination. Lists return opaque, query-bound cursors — never offsets.
• Wallet signatures are never replaced by a key. An API key authorizes preparing and submitting a transaction; the wallet still signs it. See Operations and transaction intents.
• Prediction delegation is signature-bound. A predictions:delegate key identifies the server integration, while the end user’s verified wallet signs the exact short-lived round, wallet, and price intent. See Price Predictions.
• Decimal strings. Prices and SOL amounts are canonical decimal strings; raw on-chain amounts are unsigned integer strings. Never parse them as JSON numbers.

​

Start here