Static wallet

Cobrex recommends sending every asset you support on the chosen network — e.g. for TRON use ["USDT", "TRX"]. If the user sends the wrong asset (e.g. TRX instead of USDT), funds are more likely to be recoverable without support tickets.

Create

POST https://api.cobrex.com/wallet
Content-Type: application/json

Headers

Header	Value
x-mid	Merchant ID
x-timestamp	Seconds
x-signature	HMAC for URL\ntimestamp\nJSON_body

Body

Field	Type	Description
asset	string[]	Assets within one network (see /public/assets).
network	string	Network (e.g. TRON).
client	string	Stable id for your user / wallet.
callback	string (URL)	Webhook URL for events on this address.

Sample body

{
  "asset": ["USDT", "TRX"],
  "network": "TRON",
  "client": "test1",
  "callback": "https://api.cobrex.com/webhook"
}

Sample response

{
  "wallets": [
    {
      "pid": "c-0ae60288-ebf1-11ef-b014-7cc255316480",
      "asset": {
        "name": "TRON",
        "asset": "TRX",
        "network": "TRON"
      }
    },
    {
      "pid": "c-b4ebfd16-e30f-11ef-b014-7cc255316480",
      "asset": {
        "name": "Tether USDT TRC-20",
        "asset": "USDT",
        "network": "TRON"
      }
    }
  ],
  "client": "test1",
  "address": "T9ySYRaEN1nsyefRBKsroJxtsCgog78zy1",
  "callback": "https://api.cobrex.com/webhook"
}

• wallets — internal Cobrex wallet ids per asset.
• address — one blockchain address users send to.

---

Revoking a static wallet

To stop using a previously issued address for a given client, call revoke with the wallet id from create or last fetch.

POST https://api.cobrex.com/wallet/:id/revoke

Replace :id with the identifier (e.g. tied to pid — confirm path shape with dashboard/support if needed).

Headers

Header	Value
x-mid	Merchant ID
x-timestamp	Seconds
x-signature	HMAC; if no body, URL\ntimestamp

After revoke, a new fetch for the same client may generate a new address.