Create Wallet - Finrock

curl --request POST \
     --url https://api.finrock.io/dac/v1/wallet \
     --header 'Authorization: Bearer {JWT}' \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --header 'x-api-key: YOUR_API_KEY' \
     --data '{
       "asset": "DOGE"
     }'

{
  "asset": "BTC",
  "asset_ticker": "BTC",
  "is_frozen": false,
  "balance": {
    "available": 0.025,
    "unconfirmed": 0.001,
    "frozen": 0.005
  },
  "forwarding": {
    "status": "NONE",
    "address": null,
    "frequency": "Nightly"
  },
  "wallet_type": "Legacy",
  "status": "Created",
  "requires_dt_memo": {
    "enabled": false,
    "change": "APPROVED"
  }
}

POST

dac

wallet

curl --request POST \
     --url https://api.finrock.io/dac/v1/wallet \
     --header 'Authorization: Bearer {JWT}' \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --header 'x-api-key: YOUR_API_KEY' \
     --data '{
       "asset": "DOGE"
     }'

{
  "asset": "BTC",
  "asset_ticker": "BTC",
  "is_frozen": false,
  "balance": {
    "available": 0.025,
    "unconfirmed": 0.001,
    "frozen": 0.005
  },
  "forwarding": {
    "status": "NONE",
    "address": null,
    "frequency": "Nightly"
  },
  "wallet_type": "Legacy",
  "status": "Created",
  "requires_dt_memo": {
    "enabled": false,
    "change": "APPROVED"
  }
}

MCP scope: dac.write The Create Wallet endpoint provisions a new MPC wallet for the specified asset within your sub-account. Finrock enforces a one-wallet-per-asset-per-sub-account limit, so this call is typically made once during initial onboarding for each asset you intend to support. Once provisioned, the wallet is immediately available for address generation and transaction submission.

Body Parameters

string

required

The asset for which to provision a wallet. Use the id value from the Supported Assets list (e.g. ETH, BTC, USDT_ETH).

curl --request POST \
     --url https://api.finrock.io/dac/v1/wallet \
     --header 'Authorization: Bearer {JWT}' \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --header 'x-api-key: YOUR_API_KEY' \
     --data '{
       "asset": "DOGE"
     }'

Response

A successful request returns HTTP 200 with the newly created wallet object.

string

The asset name of the wallet (e.g. BTC).

string

The ticker symbol of the asset (e.g. BTC).

boolean

Whether the wallet is frozen.

object

The wallet’s balances, in the asset’s native unit.

Show properties

number

Balance available to spend.

number

Balance from incoming transactions that are not yet confirmed on-chain.

number

Amount of the balance that is currently frozen.

object

Auto-forwarding configuration for the wallet.

Show properties

string

Auto-forwarding status: NONE, PENDING_OWNER_APPROVAL or ACTIVE. See Edit Wallet.

string | null

Destination address funds are forwarded to, or null if not set.

string

How often funds are forwarded: Nightly or RealTime.

string

The type of wallet: Legacy, HSM or MPC. See Wallet Types.

string

The wallet’s status: Creating while it’s being set up, Created when it’s ready, or Failed.

object

XRP wallets only. Whether the XRP Ledger rejects deposits to this wallet that don’t include a destination tag. Change it with Edit Wallet.

Show properties

boolean

true if deposits without a destination tag are rejected. Defaults to false. While a change is pending, this already shows the new value; check change to see whether it has been approved.

string

State of the latest change to this setting: APPROVED, or PENDING_OWNER_APPROVAL while it waits for the owner, or at least 2 admins, to approve it in the dashboard.

{
  "asset": "BTC",
  "asset_ticker": "BTC",
  "is_frozen": false,
  "balance": {
    "available": 0.025,
    "unconfirmed": 0.001,
    "frozen": 0.005
  },
  "forwarding": {
    "status": "NONE",
    "address": null,
    "frequency": "Nightly"
  },
  "wallet_type": "Legacy",
  "status": "Created",
  "requires_dt_memo": {
    "enabled": false,
    "change": "APPROVED"
  }
}

Attempting to create a second wallet for an asset that already has one in your sub-account will return an error. Retrieve your existing wallet using List Wallets first.