The CCMS API supports Basic Authentication and SSO Cookie Authentication for secure access.

This API supports two authentication methods:

Basic Authentication

Include the Authorization header with your CCMS username and API token (or password when SSO is not configured) encoded in base64. For security, tokens are recommended.

Authorization: Basic <base64(username:token)>

Example:

curl -X GET \
  'https://thunderbird.heretto.com/ezdnxtgen/api/v2/deployments' \
  -H 'Authorization: Basic ZGVtbzpocnRfYWJjMTIzWFlaNDU2'

Basic authentication is represented by the basicAuth parameter in the API endpoint specification.

SSO Cookie Authentication

Use your browser session cookie from an active Heretto CCMS login for authentication.

Cookie: JSESSIONID=<your-session-id>

Example:

curl -X GET \
  'https://thunderbird.heretto.com/ezdnxtgen/api/v2/deployments' \
  -H 'Cookie: JSESSIONID=A1B2C3D4E5F6G7H8I9J0'

Cookie authentication is represented by the ssoAuth parameter in the API endpoint specification. This method is useful when testing the API from the documentation site or integrating with browser-based tools that maintain SSO sessions.

Tip:

Browser sessions expire after inactivity. For automated workflows and server-side integrations, use Basic Authentication instead.