Thunder API – Authentication Headers

Overview

Thunder APIs use API authorization headers for authentication.

Most Thunder API requests require an Authorization header containing Base64-encoded credentials.

Required Headers

Thunder APIs commonly require the following headers:

Authorization: API {Base64EncodedCredentials}
Content-Type: application/json
Accept: application/json

Required headers may vary depending on the endpoint.

Authorization Header

The Authorization header uses the following format:

Authorization: API {Base64EncodedCredentials}

The authorization value is generated by Base64 encoding:

username:password

Example Input

user@example.com:password123

Example Encoded Value

dXNlckBleGFtcGxlLmNvbTpwYXNzd29yZDEyMw==

Resulting Header

Authorization: API dXNlckBleGFtcGxlLmNvbTpwYXNzd29yZDEyMw==

Important: The authorization value must be Base64 encoded before submission.

Common Headers

Content-Type

Used to indicate the request payload format.

Common value:

Content-Type: application/json

Accept

Used to specify the desired response format.

Common value:

Accept: application/json

Some endpoints may return XML or JSON responses. Always review endpoint-specific documentation for supported response formats.

Notes

• Credentials must be valid Thunder Cloud credentials.
• The authenticated user must have access to the requested Thunder resources.
• Some endpoints may require only a subset of headers.
• Always review endpoint-specific documentation for required headers.

Related Articles

• Thunder API – Authentication Token
• Thunder API – SaveUserUrlByGuid
• Thunder API – SaveEditURL