Authentication must be included in all Trade and POST requests made to the AIO Exchange API. The request header must include X-AIO-Auth-Type and X-AIO-Sign.
Terms And Definitions
X-AIO-Auth-Type
This is a authorization/security scheme which is defined by AIO Exchange used to process the request, the scheme used is "AIO-HMAC".
X-AIO-Sign
Any request must contain a singed header which is generated using your secret key, uri, request method, nonce, timestamp(UNIX timestamp in milliseconds ) and encoded payload combined overall with apikey, singed base64 string, nonce and timestamp.
API-Key
This key is passed along with the signed data which is supplied to you when you register with AIO Exchange.
API-Secret-Key
This key is used to generate the signed string and it is supplied to you when you register with AIO Exchange.
Nonce
This is a unique string associated to each request. This can be a Guid or a client request id.
HTTP Request Method
The HTTP request method (GET, POST, PUT, DELETE, etc.), used to make a request must be included in the signed string.
Note: These methods are case sensitive.
Request URI
This is the absolute URI where the request are made and is included in the signed string.
Payload MD5 Base64 String
Any payload sent to the API must be hashed using MD5 and parsed as a Base 64 string before being used for signing. This computed payload should then be passed into the signature string.
Request Timestamp UTC
This is the UNIX timestamp (UTC) and the count starts at the Unix Epoch on January 1st, 1970 at UTC, the unix timestamp is merely the number of seconds between a particular date and the Unix Epoch. The Max Age of a request is allowed is 180 seconds.
Signing a Request
All the request has to be signed with header as X-AIO-Sign containing signature generated.