Authentication

There are two methods for authentication:

  • Using API key and secret

  • Using signature (HMAC SHA256)

Authenticate Using API Key and Secret


To authenticate with this method, the following headers should be sent with the request:

"AEVO-KEY": `[Insert API key]`
"AEVO-SECRET": `[Insert API secret]`

Refer to API key setup to generate your API key and secret.

Authenticate Using Signature (HMAC SHA256)


👍 Keep your API secret safe!

Using signature is a safer method of authenticating since your API secret is not passed along in the requests. This prevents potential API secret leakage during transport.

To authenticate with this method, the following headers should be sent with the request:

"AEVO-TIMESTAMP": `[Insert UNIX timestamp in nanoseconds]`
"AEVO-SIGNATURE": `[Insert HMAC SHA256 signature]`
"AEVO-KEY": `[Insert API key]`
  • AEVO_SIGNATURE is generated by performing HMAC_SHA256(apiSecret, message).

  • message is a concatenation of apiKey,timestamp,httpMethod,path,body with comma separation.

  • timestamp is UNIX timestamp in nanoseconds.

  • httpMethod is HTTP method (GET, POST, DELETE). Must be uppercase.

  • apiKey, timestamp, httpMethod, path, body are all required. If the request does not have any body, use a blank space for the value of body.

Example: GET /account

  • apiKey: API_KEY

  • timestamp: 1673425955575713842

  • httpMethod: "GET" (uppercase, case sensitive)

  • path: "/account"

  • body: ""

📘 Note!

There is a trailing comma in the message, since the body of a GET request is empty.

Last updated