Get secret credentials (pre-v1.3 endpoint)
Endpoints
Get Secret Details (Old)
Pre-v1.3 Syteca ACB endpoint for retrieving secret credentials with the Access Token in the JSON request body. Superseded by GET /api/secrets//password but still supported for backward compatibility.
POST
Get secret credentials (pre-v1.3 endpoint)
Retrieves a secret’s credentials (login, password, SSH key) using the pre-v1.3 authentication model — the Access Token goes in the JSON request body, not the
Authorization header. Still supported for backward compatibility, but new consumers should use GET /api/secrets/{id}/password instead.
For ACB deployments updated from a version prior to 1.2, switch to the
https://{hostname}/EkranACB server in the Playground.Where to get the Secret ID
The Secret ID is visible on the Automation tab of the Edit Secret page — see Find the Secret ID.Permissions required
The user owning the Access Token must have at least PAM User role on the secret.Errors
See Status codes. Common errors:- 401 Unauthorized — expired or invalid Access Token.
- 403 Forbidden — user lacks the PAM User role (or higher) on this secret.
- 404 Not Found — secret doesn’t exist or isn’t visible to the authenticated user.
Related
Get secret credentials (new)
The v1.3+ equivalent with header-based auth.
Get access token
How to obtain the Access Token this endpoint requires.
API reference
Status codes, rate limiting.
Secret permissions
Role types and permission grants.
Body
application/json
Response
Credentials returned successfully