📗General

Below is the general information regarding our API URL and the tokens supported.

API URL

Make sure to use the correct API URL corresponding to the account you are using. To verify, please check your current login URL based on below.

Mainnet: https://merchant.coinsdo.com Testnet: https://merchant.coinsdotest.com/

Network	URL
Mainnet	https://open.coinsdo.com/coinsdo/open
Testnet	https://open.coinsdotest.com/coinsdo/open

Supported Networks

This is a list of networks we currently support. The code can be used as the value in 'chain' parameter in/v1/addressGet endpoint.

Code	Network
ADA	Cardano
ALGO	Algorand
ARB1	Arbitrum
ATOM	Cosmoc
AVAXC	Avalanche
BCH	Bitcoin Cash
BSC	Binance Smart Chain
BSV	Bitcoin SV
BTC	Bitcoin
DASH	Dash
DOGE	Dogecoin
DOT	Polkadot
EOS	EOS
ETC	Ethereum Classic
ETH	Ethereum
ETHW	Ethereum PoW
FIL	Filecoin
FTM	Fantom
HECO	HTX Heco
LTC	Litecoin
MATIC	Matic / Polygon
NEAR	Near Protocol
OKC	OKX
OP	Optimism
SOL	Solana
TRX	Tron
XDAI	XDai
XLM	Stellar
XRP	Ripple
ZEC	Zcash

Supported Tokens

Please refer to the currency control list in your CoinSend/CoinGet center for the most up-to-date coinsDoId.

Mainnet

coinsDoId	mainnet	protocol	tokenAddress	coinType (0-coin; 1-token)	coinName
51	ADA			0
195	ALGO			0
209	ARB1			0
210	ARB1	ARB1_ERC20	0xfd086bc7cd5c481dcc9c85ebe478a1c0b69fcbb9	1	USDT
276	ATOM			0	ATOM
53	AVAXC			0	AVAX
54	AVAXC	AVAXC_ERC20	0x9702230a8ea53601f5cd2dc00fdbc13d4df4a8c7	1	USDt
9	BCH			0	BCH
14	BSC			0	BNB
70	BSC	BEP20	0xe9e7cea3dedca5984780bafc599bd69add087d56	1	BUSD
76	BSC	BEP20	0x8ac76a51cc950d9822d68b83fe1ad97b32cd580d	1	USDC
58	BSC	BEP20	0x55d398326f99059ff775485246999027b3197955	1	USDT
278	BSV			0	BSV
1	BTC			0	BTC
4	BTC	OMNI	31	1	USDT
13	DASH			0	DASH
10	DOGE			0	DOGE
119	DOT			0	DOT
11	EOS			0	EOS
7	ETC			0	ETC
2	ETH			0	ETH
6	ETH	ERC20	0xdac17f958d2ee523a2206206994597c13d831ec7	1	USDT
18	ETH	ERC20	0x2260fac5e5542a773aa44fbcfedf7c193bc2c599	1	WBTC
196	ETHW			0	ETHW
242	FIL			0	FIL
41	FTM			0	FTM
27	HECO			0	HT
8	LTC			0	LTC
33	MATIC			0	MATIC
131	MATIC	MATIC_ERC20	0x2791bca1f2de4661ed88a30c99a7a9449aa84174	1	USDC
208	NEAR			0	NEAR
31	OKC			0	OKT
32	OKC	KIP20	0xdf54b6c6195ea4d948d03bfd818d365cf175cfc2	1	OKB
272	OP			0	ETH
273	OP	OPT_ERC20	0x94b008aa00579c1307b0ef2c499ad98a8ce58e58	1	USDT
49	SOL			0	SOL
52	SOL	SPL	Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB	1	USDT
3	TRX			0	TRX
5	TRX	TRC20	TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t	1	USDT
45	XDAI			0	XDAI
243	XLM			0	XLM
50	XRP			0	XRP
12	ZEC			0	ZEC

Testnet

coinsDoId	mainnet	protocol	tokenAddress	coinType (0-coin; 1-token)	coinName
31	ADA			0	ADA
190	ALGO			0	ALGO
204	ARB1			0	ETH
205	ARB1	ARB1_ERC20	0x68fed128b095c919ee2c4f64e5c9b9eb64974a87	1	USDT
220	ATOM			0	ATOM
116	AVAXC			0	AVAX
9	BCH			0	BCH
14	BSC			0	BNB
16	BSC	BEP20	0x337610d27c682e347c9cd60bd4b3b107c9d34ddd	1	USDT
221	BSV			0	BSV
1	BTC			0	BTC
4	BTC	OMNI	2	1	USDT
13	DASH			0	DASH
10	DOGE			0	DOGE
163	DOT			0	DOT
11	EOS			0	EOS
7	ETC			0	ETC
2	ETH			0	ETH
6	ETH	ERC20	0x378da755324ee4f1a5735a4f13499a410d82d122	1	USDT
191	ETHW			0	ETHW
213	FIL			0	FIL
25	FTM			0	FTM
17	HECO			0	HT
19	HECO	HRC20	0xd459dad367788893c17c09e17cfbf0bf25c62833	1	USDC
20	HECO	HRC20	0x04f535663110a392a6504839beed34e019fdb4e0	1	USDT
8	LTC			0	LTC
23	MATIC			0	MATIC
203	NEAR			0	NEAR
21	OKC			0	OKT
22	OKC	KIP20	0xda9d14072ef2262c64240da3a93fea2279253611	1	OKB
215	OP			0	ETH
219	OP	OPT_ERC20	0x94b008aa00579c1307b0ef2c499ad98a8ce58e58	1	USDT
29	SOL			0	SOL
100	SOL	SPL	4zMMC9srt5Ri5X14GAgXhaHii3GnPAEERYPJgZJDncDU	1	USDC
3	TRX			0	TRX
5	TRX	TRC20	TJwXPRrs39c9apaGsjccv7XiybkvYaLUhn	1	UT
27	XDAI			0	XDAI
214	XLM			0	XLM
30	XRP			0	XRP
12	ZEC			0	ZEC

How to make API request

Below are the standard rules for making an API request with the CoinsDo Open API.

Request parameters

• Header parameter

Name of parameters	Required	Type of parameters
Content-Type	Yes	application/json

• Body parameter

Name of parameters	Required	Type	Description
sign	Yes	string	Signature
data	Yes	string	Content（JSON string, depends on each API）

Signing

The signature is generated using the HMAC-SHA256 algorithm. The Secret-KEY corresponding to the API-KEY is used as the key for HMAC-SHA256 encryption of the data parameter, and the output obtained is the signature.

The following example shows the signature of the data parameter using a 1024-bit key.

{
        "data": "{\"apiKey\":\"cd384rt80f5575dc\",\"mainnet\":\"TRX\",\"targetDeviceUuid\":\"085C28EC-0BD6-442B-8232-D23BC8F4D58E\",\"timestamp\":\"1622775712229\",\"addressRemark\":\"trx address\"}",
        "sign": "852cd95d5045f3e41db0447cdde405b73cc03b8844b76da74bd0b498470cba75"
}

Respond

{
  "code": 200, // Status code
  "msg": "Success", // Remarks
  "data": null // Response 
}

Status code

Below is a general list of status codes, and each API endpoint may have its own differences.

Status code	Description
-2	System error
200	Success
4001	API endpoints not found
4002	Parameters in wrong format
4003	JSON data conversion abnormal
4004	API Key does not exists
4005	IP Restricted
4007	Signature verification failed
4010	Request expired
4068	Failed to verify APIKEY

Callback notification

Below are the details of the callback request made from CoinsDo to your endpoint.

Request Method

• POST

Request Parameters

• Header parameter

Name of parameters	Required	Type/Parameters
Content-Type	Yes	application/json

• Body parameters

Name of parameters	Required	Type	Description
sign	Yes	string	Signature
data	Yes	string	Content（JSON string）

Return example

{
  "code": 200, // Status code
  "msg": "Success", // Remarks
  "data": null // Response
}

Callback scenario

This section suggests whether you should respond to the callback.

When you execute, the return code should display 200 if the callback is successful. Once it is successful, there will be no further callbacks.

If you choose to ignore, the return code should display 202 if it is successful. There will be no callbacks (Choosing to ignore is similar to the 200 status in terms of effect. The only difference is whether you want to handle the suggested display).

Callback scenario	Example	Suggestion
Dispatch	Dispatch transaction request on the blockchain (success/rejected/cancelled).	Respond
Receiving record pending confirmation	Transaction awaiting the target number of blockchain confirmations (pending status).	Execute/ignore
Received	Target blockchain confirmations have been reached and verified successfully (final status) and credited.	Execute