How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Mesh Connect Transfers API

### Supported integrations:```Robinhood``````Coinbase``````Kraken``````CoinbasePro``````CryptoCom``````Binance``````Gemini``````OkCoin``````KuCoin``````BinanceInternational``````Bitstamp``````GateIo``````Okx``````Huobi``````Bitfinex``````KrakenDirect``````BinanceInternationalDirect``````Bybit``````Paxos``````CoinbasePrime``````DeFiWallet```### Integration-specific notes:#### Robinhood:Cryptocurrency transfers should be enabled in Robinhood settings. Transfers are disabled by default, enabling them for end users requires a review from Robinhood.Please note: * `MfaCode` parameter is required to initiate a transaction in Robinhood. * The user's security settings should be configured to use an authenticator application. * Robinhood doesn't allow initiation of transactions if the authenticator application is not configured.#### Coinbase:`MfaCode` parameter should be used to initiate transactions in Coinbase. * If the end user's Coinbase account is configured to use text messages (SMS) for two factor authentication,the API will return `MfaRequired` status, and a text code will then be sent by Coinbase. The code is expected to be provided in the subsequent call using the `MfaCode` request field * If the account is configured to use an authenticator application, the API is expecting to get thecode in the `MfaCode` request field.#### Kraken:Kraken requires the explicit chain name to be provided (e.g. `Dogecoin` or `Ethereum (ERC20)`). The list of possible chains can be obtained by calling `symbol/details` endpoint.To initiate a transaction, a Kraken Address Key name should be provided in `TargetAddress` field. Target address should be added using Kraken UI, then its name should be used.#### CoinbasePro: * CoinbasePro does not provide multiple chains per a symbol, so default chains are used for gettingDeposit addresses.#### Binance:`Enable Withdrawals` permission should be given to the user's API key to initiate transfers with Binance Us.Binance requires adding the IP address to the list of trusted IPs to be able to create API keys with transfer permission. * Please reach out to Front to get the static IP address. This address should be provided to theend user, and the user should be instructed to add it to the list of trusted IP addresses. * By default, the permission to enable withdrawals is turned off. If the end user's API key doesnot have the permission, asset transfers will not be available.#### KuCoin:KuCoin requires adding the IP address to the list of trusted IPs to be able to create API keys with transfer permission.`Fee` parameter should be used to initiate a transaction in KuCoin.Please note: * Please reach out to Front to get the static IP address. This address should be provided to theend user, and the user should be instructed to add it to the list of trusted IP addresses. * All currencies have their minimum `fee` and `amount` requirements. Please use `symbol/details`endpoint to get this data for a particular symbol. * KuCoin requires chain name to be provided for getting deposit address or initiating a cryptocurrencytransfer. Some cryptocurrencies are supported over multiple chains. It's recommended to use `symbol/details` endpoint to get the list of supported chains and show it to the end user to select a target one.#### BinanceInternational:`Enable Withdrawals` permission should be given to the user's API key to initiate transfers with Binance International.Binance requires adding the IP address to the list of trusted IPs to be able to create API keys with transfer permission. * Please reach out to Front to get the static IP address. This address should be provided to theend user, and the user should be instructed to add it to the list of trusted IP addresses. * By default, the permission to enable withdrawals is turned off. If the end user's API key doesnot have the permission, asset transfers will not be available.#### GateIo:Gate.io requires adding IP address to the list of trusted IP addresses to be able to initiate a cryptocurrency transfers.Withdrawal address should be already verified or added on the Gate.io UI (in mobile application or on the web site). * Please reach out to Front to get the static IP address for withdrawals. This address should beprovided to the end user, and the user should be instructed to add it to the list of trusted IP addresses. * Only verified withdrawal blockchain addresses are allowed for withdrawal with Gate.io API. * Gate.io requires chain name to be provided for getting deposit address or initiating a cryptocurrencytransfer. Some cryptocurrencies are supported over multiple chains. It's recommended to use `symbol/details` endpoint to get the list of supported chains and show it to the end user to select a target one.#### Huobi:Warning: Huobi does not refund executed deposits that are below the `Minimum Deposit Amount` * Please check the MinimumDepositAmount in Get Deposit Address response in order to avoid makinga deposit below the minimum amount * Huobi does not allow withdrawals to addresses that are not white-listed, please add the addressthat you would like to withdraw to the white list of addresses through the UI so that a withrawal can be processed#### Bitfinex: * The hash of transfer is not available when making a transfer in Bitfinex. To get the hash pleasere-query the transfer using the transaction id. * Bitfinex does not separate sub-accounts when returning the list of transfers.Therefore the samelist of transfers is returned for all Bitfinex sub-accounts.#### KrakenDirect:Kraken requires the explicit chain name to be provided (e.g. `Dogecoin` or `Ethereum (ERC20)`). The list of possible chains can be obtained by calling `symbol/details` endpoint.To initiate a transaction, a Kraken Address Key name should be provided in `TargetAddress` field. Target address should be added using Kraken UI, then its name should be used.

Mesh Connect Transfers API is one of 12 APIs that Mesh Connect publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transfers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 5 operations across 5 paths, and defines 25 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://admin-api.meshconnect.com.

5 operations 5 paths 25 schemas 5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://integration-api.meshconnect.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Mesh Connect Transfers API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (Bearer). By default, every request must be authenticated.

  • Bearer — Authorization header using the Bearer scheme. Example: "Authorization: Bearer {Value}"

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 5 POST. Each is listed below with its method, path, parameters, and response codes.

Transfers 5

Supported integrations: Robinhood Coinbase Kraken CoinbasePro CryptoCom Binance Gemini OkCoin KuCoin BinanceInternational Bitstamp GateIo Okx Huobi Bitfinex KrakenDirect BinanceIn…

POST
/api/v1/transfers/list
Get transfer history
body → 200400401403
POST
/api/v1/transfers/details
Get transfer details
body → 200400401403404
POST
/api/v1/transfersdeprecated
Initiate a transfer
body → 200400401403
POST
/api/v1/transfers/address/get
Get deposit address
body → 200400404401
POST
/api/v1/transfers/symbol/details
Get details of asset
body → 200400404401

Schemas 25

The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are B2BBrokerCryptocurrencyTransaction (19 properties), TransfersBrokerCreateCryptocurrencyTransactionRequest (15 properties), B2BBrokerCreateCryptocurrencyTransactionResponse (9 properties), B2BBrokerCryptocurrencyDepositAddressResponse (8 properties). Each schema is shown below with its type and property counts.

B2BBrokerTransactionsListModelApiResult
object
6 properties
B2BBrokerCryptocurrencyDepositAddressResponseApiResult
object
6 properties
B2BBrokerCreateCryptocurrencyTransactionResponse
object
9 properties
B2BBrokerCryptocurrencyTransaction
object
19 properties
MfaType
string
B2BBrokerTransactionsListModel
object
4 properties
B2BBrokerCreateCryptocurrencyTransactionResponseApiResult
object
6 properties
BrokerCryptocurrencyChain
object
7 properties
BrokerResponseStatus
string
BrokerCryptocurrencyTransactionBlockchainMethod
string
B2BBrokerCryptocurrencyTransactionApiResult
object
6 properties
B2BBrokerCryptocurrencySymbolDetailsResponse
object
3 properties
BrokerCryptocurrencyTransactionNetworkFee
object
4 properties
B2BBrokerCryptocurrencySymbolDetailsResponseApiResult
object
6 properties
BrokerCryptocurrencyTransactionStatus
string
TransfersBrokerCryptocurrencyTransactionDetailsRequest
object
6 properties 2 required
TransfersBrokerCryptocurrencyDepositAddressRequest
object
6 properties 2 required
BrokerType
string
ApiResultStatus
string
TransfersBrokerTransactionsListRequest
object
7 properties 2 required
ApiResult
object
5 properties
CryptocurrencyAddressType
string
TransfersBrokerCreateCryptocurrencyTransactionRequest
object
15 properties 3 required
B2BBrokerCryptocurrencyDepositAddressResponse
object
8 properties
BrokerCryptocurrencyTransactionType
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mesh-connect-transfers-api-openapi.yml Raw ↑

Other APIs Mesh Connect publishes across the network.

Mesh Connect Assets API
Mesh Connect Auth token API
Mesh Connect Balance API
Mesh Connect BrokerAccountDetail API
Mesh Connect Main Clients API
Mesh Connect Managed Account Authentication API
Mesh Connect Managed Transfers API
Mesh Connect Portfolio API
Mesh Connect Registered Clients API
Mesh Connect Self Managed Account Authentication API
Mesh Connect Transactions API
Where this information came from

This is an independent, third-party profile of Mesh Connect Transfers API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.