Create a Digital Asset Wallet

curl --request POST \
  --url https://api-sandbox.finogates.com/v1/platform/digital-assets/wallets \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "user_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "asset_code": "<string>",
  "network_code": "<string>"
}
'

{
  "status_code": 123,
  "data": "<unknown>",
  "query_generated_time": 123
}

Create Digital Asset Wallet

Create a digital asset wallet (a deposit address) for one of your users — or get the existing one back if it was already created.

Every new asset-and-network combination must first be approved by Finogate’s team. When you ask for a new one, this returns straight away with a request ID and a “waiting for approval” status. Once the team approves it, the wallet is created for you automatically — you do not need to call this again. If you ask for a wallet that already exists, its deposit address is returned right away.

Some assets also need a small amount of a separate “gas” asset to cover network fees. When that applies, the response includes a gas_dependency section so you can prompt the user to top it up.

Warning: sending a digital asset on the wrong network is usually lost for good. The response gives you both the deposit address and its network_code (such as ethereum or tron). Users must send funds on the exact network the address belongs to. Sending an asset from a different blockchain — for example USDT on Tron to an Ethereum address, or Bitcoin to an Ethereum-style address — loses the money for good, because it never reaches us and cannot be recovered. Always show the network clearly on any deposit screen you build.

POST

/

v1

/

platform

/

digital-assets

/

wallets

Create a Digital Asset Wallet

curl --request POST \
  --url https://api-sandbox.finogates.com/v1/platform/digital-assets/wallets \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "user_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "asset_code": "<string>",
  "network_code": "<string>"
}
'

{
  "status_code": 123,
  "data": "<unknown>",
  "query_generated_time": 123
}

Authorizations

Authorization

string

header

required

The access token received from the authorization server in the OAuth 2.0 flow.

Body

application/json

Request body for POST /platform/digital-assets/wallets.

user_id

string<uuid>

required

End-user public UUID under the authenticated platform.

asset_code

string

required

Catalog asset code, e.g. usdt, btc, eth.

Required string length: 1 - 50

Example:

"usdt"

network_code

string

required

Catalog network code, e.g. ethereum, tron, bitcoin.

Required string length: 1 - 50

Example:

"tron"

Response

Successful Response

Standard response wrapper for single-object responses and errors.

Generic over the payload type. A route that declares CommonResponse[SomeModel] gets the real data schema rendered in OpenAPI/Swagger; a bare CommonResponse leaves data untyped.

status_code

integer

required

HTTP status code for the response.

data

any

required

Payload or error details.

query_generated_time

integer

required

UTC timestamp (milliseconds since epoch) when response was generated.

List Digital Asset Wallets List Digital Asset Balances