Mobile Api
System Bootstrap
Bootstrap request encryption and read the currently supported blockchain networks.
Flow Summary
The current system-bootstrap flow is:
Step 1. Generate an encryption key pairPOST /api/v2/sys/key-pair
Step 2. Load supported blockchain networksGET /api/v2/sys/networks
Both routes are public and do not require Authorization.
1. When To Use This Module
Use these endpoints during app bootstrap when you need to:
- start the optional encrypted-request handshake before sending sensitive JSON payloads
- display which blockchain deposit or settlement networks the mobile app currently supports
2. Generate Encryption Key Pair
POST /api/v2/sys/key-pair
Send the mobile client public key so the server can generate a temporary server key pair for encrypted request exchange.
Request body
{
"key": "base64-encoded-32-byte-client-public-key"
}
Validation rules
keyis required- the value must be valid Base64
- after Base64 decode, the key must be exactly
32bytes
Success response
{
"status_code": 200,
"message": "Success",
"data": {
"server_pub_key": [12, 44, 91, 7],
"key_version": "f7e7a0be-1742-4d8c-9c7d-bf32f23f88c1"
}
}
Important backend behavior
server_pub_keyis returned as a JSON array of32integers, not a Base64 stringkey_versionis returned as a UUID string; send this raw value back later in the encrypted wrapper- the generated key pair is intended for short-lived use and should be refreshed if the client waits too long before sending encrypted payloads
- bootstrap requests normally use plain JSON because this call creates the first key pair
Error caveat
- invalid client keys return an error response
3. Get Supported Networks
GET /api/v2/sys/networks
Returns the blockchain networks currently exposed to the mobile app.
Success response
{
"status_code": 200,
"message": "Success",
"data": {
"networks": [
{
"name": "Tron (TRC20)",
"code": "TRC20"
}
],
"description": "Supports Tron (TRC20) network only"
}
}
Important backend behavior
- the current response includes one supported network:
TRC20 descriptionis localized when available
Integration Notes
- Call
POST /api/v2/sys/key-paironly when the client really needs encrypted request payloads. - Re-bootstrap the key pair if the client waits longer than
30minutes before sending the encrypted request. - Treat
GET /api/v2/sys/networksas the source of truth for supported network options instead of hardcoding future assumptions.