Skip to main content
This page documents the request and response schemas that appear across multiple ACB endpoints. Field-by-field notes for each endpoint live on the endpoint pages; this page is the canonical reference for the shared schemas.
All field names use snake_case (e.g. parent_folder_id, rotate_every_min). Boolean defaults are false unless otherwise noted.

Enums

SecretType

The type of credential a secret represents. Determines which other fields are required vs ignored.

PasswordRotationStatus

The state of rotation for a secret’s password. Read-only in API responses.

PasswordCheckStatus

The result of the last heartbeat password check on a secret. Read-only.

PasswordCheckPeriodType

Period type for heartbeat check intervals.

Configuration objects

Permissions

Container for the list of permissions granted on a folder or secret.

Permission

A single permission grant assigning a role to a user or user group on the resource.

AdditionalFeature

Optional features configurable per secret (e.g. file transfer access).

FileTransfer

Configuration for file transfer alongside SSH sessions.

Rotation

Password rotation configuration. Changed in v1.4: rotate_every_min is now required with minimum: 1 — the v1.3 default of 0 (disabled) is no longer accepted in this field; use enabled: false instead.

CheckOut

Check-out / check-in workflow configuration for shared secrets.

CheckPassword

NEW in v1.4 — Heartbeat password checking configuration.

RequireApproval

Approval workflow configuration for high-sensitivity secrets.

PasswordData

Used in request bodies when setting a secret’s password.

SshKey

Used in request bodies when setting a secret’s SSH key (UnixAccountSSH type).

Response shapes

FolderResponseDto

Returned by GET /api/folders/{id} and POST /api/folders.

SecretPasswordlessResponseDto

Returned by GET /api/secrets/{id}, POST /api/secrets, and PATCH /api/secrets/{id}. Does not include the actual password value — to retrieve credentials use Get secret credentials.

Required vs ignored fields by SecretType

When creating a secret with Add secret, the relevance of each field depends on the type value: Fields marked are ignored by the API for that secret type. See Add secret for the per-type request examples.

API reference

Base URL, authentication, status codes, rate limiting.

Add secret

The endpoint that consumes most of these schemas in request bodies.

Secret permissions

Owner / Editor / PAM User roles and how they’re applied.

Heartbeat

The NEW v1.4 password-validity check endpoint.