For the complete documentation index, see llms.txt.
Skip to main content
Version: 8.10 (unreleased)

Resolve secrets (alpha)Added in 8.10

POST 
/secrets/resolve

Strongly Consistent About endpoint data consistency

Resolve a deduplicated batch of camunda.secrets.* references for the caller's physical tenant in a single round-trip.

Each reference is authorized and resolved independently. For valid requests, the endpoint always responds with HTTP 200: successfully resolved references are returned in resolved, while references that could not be resolved (for example not found, malformed or over-long, or the caller lacks SECRET:REVEAL on that reference) are returned in errors. A failure of one reference never fails the others. Only structurally invalid requests are rejected with HTTP 400: a missing or non-array references field, more than 20 references, or a null entry.

References are resolved against the secret stores configured for the caller's physical tenant, served from the gateway's secret cache when the value is already cached and read from the store otherwise.

This endpoint is an alpha feature and may be subject to change in future releases.

Required permissions​

When authorization is enabled, this endpoint requires the following permission. See resources and permissions to learn more.

Resource typePermission
SECRETREVEAL

Results you are not authorized to access are filtered from the response rather than rejected.

Request​

Responses​

The batch was processed. Per-reference outcomes are split between resolved and errors; this status is returned even when some or all references failed.