Authorizations
Contact Mesh to get client Secret
Contact Mesh to get client Id
Body
The authentication token to send the asset from.
1
The type of the integration to send the asset from.
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
Id of the Preview of the transfer.
Multi-factor auth code that should be provided if the status of the transfer was MfaRequired
.
When user is unable to provide the primary Mfa this should be passed in to use fallback Mfa.
Response
OK
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.