Check secret password (Heartbeat)
Endpoints
Heartbeat (Check Password)
Syteca ACB REST API endpoint — NEW in v1.4 — to verify a secret’s password is still valid on the target endpoint without modifying it. Useful for detecting drift between Syteca and the target system.
POST
Check secret password (Heartbeat)
NEW in ACB v1.4. Not available in v1.3 and earlier. Confirm your installed ACB version supports this endpoint before scripting against it.
For ACB deployments updated from a version prior to 1.2, switch to the
https://{hostname}/EkranACB server in the Playground.Permissions required
The user owning the Access Token must have Editor or Owner role on the secret.Status values returned
The response includes acheck_password_status field with one of four PasswordCheckStatus values:
None— No check has been performed yet.Valid— The password is valid on the target endpoint.Invalid— The password is not valid (drift detected — consider rotating).Failed— The check itself failed (target unreachable, network error, etc.).
Errors
- 403 Forbidden — user lacks Editor/Owner role.
- 404 Not Found — secret doesn’t exist.
Related
Get secret
Read scheduled heartbeat results via
check_password_status.Rotate password
If heartbeat returns Invalid, rotate to fix drift.
Data models — CheckPassword
Schedule heartbeat checks per secret.
Data models — status enum
PasswordCheckStatus values.
Authorizations
Access token for authentication
Path Parameters
The ID of the secret to check
Required range:
x >= 1Response
Heartbeat check completed successfully
Status of the last password check (heartbeat)
Available options:
None, Valid, Invalid, Failed