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.
This endpoint is an alpha feature and may be subject to change in future releases.
Phase 1: the secret backend is mocked. Only a fixed allow-list of references resolves;
every other authorized, valid reference returns NOT_FOUND.
Request
Responses
- 200
- 400
- 401
- 500
- 503
The batch was processed. Per-reference outcomes are split between resolved and
errors; this status is returned even when some or all references failed.
The provided data is not valid.
The request lacks valid authentication credentials.
Response Headers
An internal error occurred while processing the request.
The service is currently unavailable. This may happen only on some requests where the system creates backpressure to prevent the server's compute resources from being exhausted, avoiding more severe failures. In this case, the title of the error object contains RESOURCE_EXHAUSTED. Clients are recommended to eventually retry those requests after a backoff period. You can learn more about the backpressure mechanism here: https://docs.camunda.io/docs/components/zeebe/technical-concepts/internal-processing/#handling-backpressure .