secrets.groups.listThe group tree with how many secrets each group holds
GET /secrets/api/groupsIAM secrets:ListSecretsRead
Counts include every group below. A group exists while a secret is filed in it; move secrets with `secrets update --group` or `secrets bulk-move`.
Request syntax
GET /secrets/api/groupsResponse
200 with { roots, ungrouped, total }: roots is the tree, each node { path, label, count, children }; counts are of secrets the caller may describe.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow secrets:ListSecrets on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud secrets groups listcurl -X GET "https://console.platform-development.deutschecloud.app/secrets/api/groups" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_secrets_groups_list.