diff --git a/anboto-trading-api-2.0.yml b/anboto-trading-api-2.0.yml
index 46a5a53..2183ac8 100644
--- a/anboto-trading-api-2.0.yml
+++ b/anboto-trading-api-2.0.yml
@@ -1,9 +1,12 @@
+---
openapi: 3.0.1
info:
title: Anboto Trading API
description: "Anboto Trading API
Authentication
Please visit\
\ Anboto's website to generate an API key
Mainnet:
- https://api.trade.anboto.xyz
Testnet:
\
+ https://api.trade.anboto.xyz\">https://api.trade.anboto.xyz
Pro:
- https://api.pro.anboto.xyz (Settings API)
Testnet:
\
\ - https://api.testnet.anboto.xyz
\
\ (All trades are simulated on testnet and will not trade on any real\
\ exchange)
Select Your API Key Type
1) System-generated\
@@ -22,10 +25,12 @@ info:
\ steps:
1. The string to sign should be a concatenation of 'timestamp\
\ + API key + (recv_window) + (queryString | jsonBodyString)' The queryString\
\ should be assembled in alphabetical order.
2. Take your secret key and decode\
- \ from Base664 into a byte array and then use the HMAC_SHA256 (for system generated\
- \ keys) or RSA_SHA256 algorithm to sign the string in step 1.
3. Convert the\
- \ signed value to a hex string (HMAC_SHA256) / base64 (RSA_SHA256) to obtain the\
- \ sign parameter.
4. Append the sign parameter to request header, and send\
+ \ from Base64 into a byte array (standard Base64 if the secret contains +, /, or\
+ \ ends with =; otherwise URL-safe Base64 with padding). Then use HMAC_SHA256\
+ \ (for system generated keys) or RSA_SHA256 algorithm to sign the string in step\
+ \ 1.
3. For HMAC keys, set X-SIGN to standard Base64 of the digest (not hex).\
+ \ For RSA keys, use Base64 of the signature.
4. Append the sign parameter to\
+ \ request header, and send\
\ the HTTP request.
Examples can be found here: https://github.com/anbotolabs/examples
The OpenAPI spec can be found here:\
\