Network Fee Interface
Return network fee of target token
POST https://admin.ccpayment.com/ccpayment/v1/network/fee
Headers
Timestamp*
string
Timestamp in seconds (10-digit). The request is valid for two minutes.
Content-Type
String
application/json; charset=utf-8
Request Body
token_id*
string
Token ID for the target token. Get token id by calling interface or checking it on the sheet
address
string
If this parameter is passed, CCPayment will tell whether it is an internal or external address. The network fee for an internal address is 0.
Response
Header
Appid
202302010636261620672405236006912
Y
string
Merchant's unique credential. Find it on the Developer page.
Timestamp
1677152490
Y
string
Timestamp in seconds (10-digit). The request is valid for two minutes.
Sign
871f0223c66ea72435208d03603a0cb00b90f6ac4a4ba725d00164d967e291f6
Y
string
SHA-256 (appId + appSecret + timestamp+body (json string))
Body
{
"code": 10000,
"msg": "success",
"data": {
"token_id": "f137d42c-f3a6-4f23-9402-76f0395d0cfe",
"crypto": "USDT",
"fee":"0.0344"
}
}Parameters
code
10000
Integer
msg
Success
String
data
Object
data.token_id
f137d42c-f3a6-4f23-9402-76f0395d0cfe
String
Token ID for the target token. Get token id by calling interface or checking it on the sheet
data.crypto
USDT
String
data.fee
0.0344
string
Network fee
{
"code": 224066,
"msg": "service err, please try again"
}As a security measure, we will sign the returned data (and according to this only { code: 10000 } should be signed, but it's signing all the returned body.). Additionally, it will return Appid, Sign, Timestamp in the header of the response. The signature method SHA-256 (appid+appSecret+Timestamp+body).
Please use the data with caution if the signature verification fails. It indicates that the data has been tampered with.
Request Body Example
{
"token_id": "f137d42c-f3a6-4f23-9402-76f0395d0cfe",
"address":""
}The body of HTTP is a json string .
Add the content in body of HTTP to the signature. Ensure the body content matches the signature content. As soon as CCPayment receives the request, the body content will be read and the signature will be verified.
Last updated