Skip to main content
Version: 8.5 / 3.13.0

Authentication

All Optimize API requests except the health readiness endpoint require authentication. To authenticate, generate a JSON Web Token (JWT) and include it in each request.

Generate a token

  1. Create client credentials in the Clusters > Cluster name > API tab of Camunda Console.
  2. Add permissions to this client for Optimize.
  3. Once you have created the client, capture the following values required to generate a token:
    NameEnvironment variable nameDefault value
    Client IDZEEBE_CLIENT_ID-
    Client SecretZEEBE_CLIENT_SECRET-
    Authorization Server URLZEEBE_AUTHORIZATION_SERVER_URLhttps://login.cloud.camunda.io/oauth/token
    Optimize REST AddressCAMUNDA_OPTIMIZE_BASE_URL-
    caution

    When client credentials are created, the Client Secret is only shown once. Save this Client Secret somewhere safe.

  4. Execute an authentication request to the token issuer:
    curl --request POST ${ZEEBE_AUTHORIZATION_SERVER_URL} \
    --header 'Content-Type: application/x-www-form-urlencoded' \
    --data-urlencode 'grant_type=client_credentials' \
    --data-urlencode 'audience=optimize.camunda.io' \
    --data-urlencode "client_id=${ZEEBE_CLIENT_ID}" \
    --data-urlencode "client_secret=${ZEEBE_CLIENT_SECRET}"
    A successful authentication response looks like the following:
    {
    "access_token": "<TOKEN>",
    "expires_in": 300,
    "refresh_expires_in": 0,
    "token_type": "Bearer",
    "not-before-policy": 0
    }
  5. Capture the value of the access_token property and store it as your token.

Use a token

Include the previously captured token as an authorization header in each request: Authorization: Bearer <TOKEN>.

For example, to send a request to the Optimize API's "Get dashboard IDs" endpoint:

tip

The ${CAMUNDA_TASKLIST_BASE_URL} variable below represents the URL of the Optimize API. You can capture this URL when creating an API client. You can also construct it as https://${REGION}.optimize.camunda.io/${CLUSTER_ID}.

curl --header "Authorization: Bearer ${TOKEN}" \
-G --data-urlencode "collectionId=${COLLECTION_ID}" \
${CAMUNDA_OPTIMIZE_BASE_URL}/api/public/dashboard

A successful response includes dashboard IDs. For example:

[
{
"id": "11111111-1111-1111-1111-111111111111"
},
{
"id": "22222222-2222-2222-2222-222222222222"
}
]

Token expiration

Access tokens expire according to the expires_in property of a successful authentication response. After this duration, in seconds, you must request a new access token.