Skip to main content
POST
Force check-in secret
Forcibly checks in a secret that’s currently checked out by another user or automation. Used when an automation pipeline crashed without checking in, when a user has left and held checked-out secrets, or when administrative intervention is required to free up a high-contention secret.
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 Owner role on the secret. The original checker-out can be a different user — force check-in is the administrative override.

Auto-rotation on force check-in

If the secret’s CheckOut configuration has rotate_on_checkin: true, force check-in also rotates the password — protecting against the scenario where the previous checker-out may have leaked the credential.

Errors

See Status codes. Common errors:
  • 403 Forbidden — user lacks Owner role.
  • 404 Not Found — secret doesn’t exist.
  • 409 Conflict — secret is not currently checked out.

Get secret

Check current check-out state.

Update secret

Modify check-out configuration.

Rotate password

Standalone rotation if force-checkin didn’t auto-rotate.

Data models — CheckOut

CheckOut schema.

Authorizations

Authorization
string
header
required

Access token for authentication

Path Parameters

id
integer<int32>
required

The ID of the secret to force check-in

Required range: x >= 1

Response

Secret checked in successfully