Developers

From your wallet to your workflow.

Read balances, request addresses and follow transactions through the API. Use webhooks to bring payment events into your application.

Create wallet Documentation

Your first request

Create an API key with balances.read permission and allow your server IP. Set API_URL to this deployment and API_TOKEN to your key. This read-only request returns your wallets.

GET /api/v1/wallets

curl "$API_URL/api/v1/wallets" \
  -H "Authorization: Bearer $API_TOKEN" \
  -H "Accept: application/json"

HTTP · JSON · Bearer token

401: check the key. 403: check permissions and the IP allowlist. 429: check rate and usage limits. If request signing is enabled, include the HMAC headers described in the documentation.

Webhooks

Verify the webhook HMAC signature before processing an event. Handle retries idempotently so the same payment is not fulfilled twice. IP filtering is a separate protection layer.

Separate controls for API access

API & SDK

Start with the HTTP API and the OpenAPI reference below. A public SDK release is not yet available through the linked repositories. Sending funds requires a local signer.

Documentation

Public API documentation is available without signing in. Administrative API documentation requires an authorized account.

Make room for your next move.

Create an account, then set up the wallet on your device and save your recovery phrase.

Create wallet