Transfer Wallet API
This guide is for TRANSFER-mode agents building their own website — your backend calls best-system's member API server-to-server only.
Three things to prepare
- In bo-web, open Api Management → API Credential, turn on the External Site API switch and set the IP allowlist (your server's outbound IPs)
- Store these 3 values as environment variables on your backend:
| Value | Format |
|---|---|
BASE_URL | https://api.example.com (provided by the best-system team per environment) |
API_KEY | ak_ followed by 48 hex chars |
API_SECRET | 64 hex chars — server-side only |
- Sign every request with
X-Api-Key+ HMAC per Authentication
Every endpoint lives under BASE_URL/api/v1 and returns the same envelope { success, code, message, data, request_uuid } — success means code === 0 (see Conventions)
Read next
- All endpoints — every endpoint with request/response examples
- Authentication — S2S signing + the member-token lifecycle + test vectors
- Conventions — base URL, envelope, rate limit
- Business codes — the full result-code catalog