Skip to content
DAZZM documentationDAZZM documentationDAZZM documentation

API authentication

Updated on Published on

Article summary

Authenticate DAZZM API calls with a token sent via HTTPS POST and a JSON payload. Each endpoint (production, test, and QA) uses a different token. DAZZM can revoke tokens and issue new ones upon request.

Protocol and Format

Section titled “Protocol and Format”

This service is invoked via an HTTPS/SSL POST request with a JSON-formatted payload.

Authentication and Encryption

Section titled “Authentication and Encryption”

Authentication is performed using a token. Each endpoint (production, test, and QA) uses a different token. This token allows the DAZZM platform to authenticate API calls. Upon request, DAZZM can revoke existing tokens and/or issue new ones.

Encryption is handled by the transport layer (HTTPS/SSL) and does not require any specific configuration, such as tunnels or custom certificates.

Example

Section titled “Example”

Example of invoking the service using JavaScript/Node.js:

fetch("https://your_environment.octopus-esm.com/api/prod/the-service", {
  "headers": {
   {


    "api-key": "le-token",


    "content-type": "application/json;charset=UTF-8"


  },


  "body": "{\"data\":\"test\"}",


  "method": "POST"


});