auth keys

Sign in for Tokens, AuthKeys and learning resources.

Service Tokens

Supply header [name:connection-token] along with your connection_string when starting these channels.

Affinity M-Queue 
Use API Mmethod create_blockchain_mq or sign in for existing.
Global Context 
Start your new application with API Method: add_application.
API AuthKey 
PUBLIC_ID

[:~]
API_SECRET
[:~]

These keys are needed to authenticate requests with the API endpoint, sign your payload using the HMAC-SHA512 method and include the following headers.

API MethodsHTTP POST 
[API Endpoint] https://api.async360.com

[Add Header] public-id: YOUR_PUBLIC_ID

[Add Header] sign: HEX_ENCODED_SIGNATURE

NETWORKS
[:~]
Node.js 
const crypto = require("crypto");
const message = {
  "method": "create_blockchain_mq",
  "params": {
   "queue_name": "new-processor"
 },
};
const sign = crypto.createHmac('sha512', apiSecret)
.update(JSON.stringify(message)).digest('hex');
C# .Net 
string GetHeaderSign(string obj)
{
  var hmac = new HMACSHA512(Encoding.UTF8.GetBytes(API_SECRET));
  byte[] hash = hmac.ComputeHash(Encoding.UTF8.GetBytes(obj));
  return hash.ToHex();
}
client.DefaultRequestHeaders.Add("public-id", PUBLIC_ID);
client.DefaultRequestHeaders.Add("sign", GetHeaderSign(obj.ToString()));