Authorizations
Contact Mesh to get client Secret
Contact Mesh to get client Id
Body
Auth token that allows connecting to the target institution
1
Type of the institution to connect
Supported integrations:
Robinhood
Coinbase
Kraken
CryptoCom
Binance
Gemini
OkCoin
KuCoin
BinanceInternational
Bitstamp
GateIo
Okx
Huobi
Bitfinex
KrakenDirect
BinanceInternationalDirect
BitfinexDirect
Bybit
Paxos
CoinbasePrime
BtcTurkDirect
ParibuDirect
RobinhoodConnect
BlockchainCom
BinanceConnect
RevolutConnect
BinancePay
BybitDirect
ParibuOAuth
PayPalConnect
CoinbaseRamp
BybitDirectMobile
DeFiWallet
robinhood
, eTrade
, alpaca
, tdAmeritrade
, weBull
, stash
, interactiveBrokers
, public
, coinbase
, kraken
, coinbasePro
, cryptoCom
, openSea
, binanceUs
, gemini
, cryptocurrencyAddress
, cryptocurrencyWallet
, okCoin
, bittrex
, kuCoin
, etoro
, cexIo
, binanceInternational
, bitstamp
, gateIo
, acorns
, okx
, bitFlyer
, coinlist
, huobi
, bitfinex
, deFiWallet
, krakenDirect
, vanguard
, binanceInternationalDirect
, bitfinexDirect
, bybit
, paxos
, coinbasePrime
, btcTurkDirect
, kuCoinDirect
, okxOAuth
, paribuDirect
, robinhoodConnect
, blockchainCom
, bitsoDirect
, binanceConnect
, binanceOAuth
, revolutConnect
, binancePay
, bybitDirect
, paribuOAuth
, payPalConnect
, binanceTrDirect
, coinbaseRamp
, bybitDirectMobile
, sandbox
Target address to transfer the asset to
1
Additional data to send on-chain (optional, depends on an integration)
Amount to transfer
On-chain fee (optional, depends on an integration)
Type of the address of symbol to be transferred. Providing EthAddress
will initiate a transfer of ETH over Ethereum blockchain.
Can be used instead of Symbol
and Chain
fields.
To transfer assets over non-default chains (e.g. sending USDT over ERC20) please Symbol
and Chain
fields.
ethAddress
, btcAddress
, ltcAddress
, solAddress
, algoAddress
, celoAddress
, cardanoAddress
, polygonAddress
, bnbAddress
, elrondAddress
, neoAddress
, xrpAddress
, flowAddress
, harmonyOneAddress
, tronAddress
, dogeAddress
, opAddress
2 Factor auth code (optional, depends on an integration)
Travel rule transaction id (optional, depends on an integration)
2 Factor auth type (optional, depends on an integration)
phone
, email
, totp
, phoneAndEmail
, requireNextSecurityQuestion
, readEmail
, face
, tradingPin
, qrCode
, password
, roaming
, mobile
, passkey
Password or pass-phrase, required to send transfers (optional, depends on an integration)
Custom chain name, required by some of the integrations. E.g. USDT can be sent over USDT-ERC20, USDT-TRC20, and USDT-Omni.
Can be used to transfer assets over non-default chains (e.g. sending USDT over ERC20).
Please use symbol/details
endpoint to get the list of all possible chains.
Memo (also called "Tag") - address remark.
Symbol to be transferred. Can be provided instead of the AddressType
field.
Store the preview id to be used for the transaction. Can be used as idempotency key for external API calls.
Response
Transfer successfully initiated.
ok
, serverFailure
, permissionDenied
, badRequest
, notFound
, conflict
, tooManyRequest
, locked
, unavailableForLegalReasons
A message generated by the API
User-friendly display message that can be presented to the end user
An error grouping hash from string components and caller information. Used by bugsnag on FE for correct error grouping
Strictly-typed error type that is explaining the reason of an unsuccessful status of the operation. All possible error types are available in the documentation.