Build with BroLabel.

Integrate with the production BroSettlement API, Ed25519 authentication, and WebSocket events. Register to get started, or explore the sandbox demo with simulated data.

View Sandbox DemoRead API Docs
REST + WebSocketEd25519 authSimulated demoOpenAPI spec
api.brolabel.io / sandboxHTTP 201
# Create a wallet in seconds
POST  /v1/wallets
Authorization:  Ed25519 {signature}

{
  "blockchain": "ETH",
  "label": "my-first-wallet"
}

// Response 201
{
  "id": "w_9f3k2...",
  "address": "0x1a2b3c...",
  "blockchain": "ETH",
  "status": "active"
}

Review the flow in 3 steps.

01

Review the Ed25519 model

The documentation explains key-pair generation and request signing. The private key is intended to remain in the client environment.

# Generate key pair
openssl genpkey -algorithm ed25519 \
  -out private_key.pem
openssl pkey -in private_key.pem \
  -pubout -out public_key.pem
02

Explore wallet operations

Review the POST /v1/wallets request structure and example responses. The demo console shows simulated wallets and operations only.

curl -X POST \
  https://api.brolabel.io/v1/wallets \
  -H "Authorization: Ed25519 {sig}"\
  -d '{ "blockchain": "ETH" }'
03

Plan event handling

Use the WebSocket documentation to subscribe to events for your organization and handle transaction lifecycle updates.

wss://api.brolabel.io/events
// Streams in real time:
← "deposit.confirmed"  { amount, wallet_id }
← "withdrawal.completed"{ tx_hash, fee }
← "aml.flagged"       { wallet_id, reason }

Copy, adapt, prepare your integration.

brolabel-api.sh
# Create a wallet
curl -X POST \
  https://api.brolabel.io/v1/wallets \
  -H "Authorization: Ed25519 {signature}" \
  -H "Content-Type: application/json"  \
  -d '{
    "blockchain": "ETH",
    "label": "user-wallet-001"
}'

Prepared for production integration.

01

Ed25519 per-request signing

Every request signed with your Ed25519 private key — asymmetric, per-request. No shared secrets, no API keys in plaintext.

02

IP whitelisting + replay protection

Restrict API access to your server IPs. Nonce-based validation helps prevent signed requests from being reused.

03

REST + WebSocket

Synchronous REST for wallet and transaction operations. Real-time WebSocket for deposit confirmations, withdrawals, and AML alerts.

04

5 RBAC roles

Owner, Admin, Operator, Reader, Service — enforce separation of duties at the API level. Map roles to your org structure.

05

Demo console with simulated data

Explore sample wallets, transactions, and events without real API operations, keys, balances, or testnet tokens.

Integration resources.

API Documentation

API concepts, schemas, Ed25519 signing, and request examples for your integration.

Available

Sandbox Demo

An interactive demo console with simulated wallets, transactions, and events. Register in the BroSettlement app for real API operations.

Demo

Swagger Collection

The production Integration API contract with endpoints, request schemas, and responses.

Open Swagger ↗

AI Agent Skill

Guided onboarding, Co-Signer setup, and signed API operations with BroSettlement Agent Skills.

Available

Ed25519 authentication for every request.

Ed25519 asymmetric signing authenticates each request without shared secrets or long-lived tokens. Nonce-based validation helps prevent replay attacks.

Provider
Auth Method
Replay Protection
Shared Secrets
USBroLabel
Ed25519 asymmetric per-request
✓ Nonce-based
✓ None
Fireblocks
API key + JWT (1hr sessions)
Partial
✗ API key in headers
Utila
JWT token (hour-long sessions)
✗
✗ JWT bearer token
Safeheron
RSA + Hardware token required
✓
✗ Hardware dependency
Fystack
Shared secret HMAC
✗
✗ Shared secret

Questions? Talk to an engineer.

Talk to an engineer about your architecture, Co-Signer setup, and production API integration.

Book Technical CallView Sandbox Demo