Secrets

In Cerby, secrets are encrypted digital records that contain sensitive corporate data in text and attached files. A secret object contains information about the secret title, its ID, its category, if it requires a challenge, the workspace where it belongs, the dates when the secret was created and last updated, and the user who created and last updated the secret.

A secret object is created in Cerby when you perform any of the following actions:

  • Add a secret manually through the Cerby web app or mobile app.

  • Import items from your password manager.

With the Cerby API, you can retrieve all secrets or specific secrets by providing their ID. To learn more about secrets, refer to the Secretsarrow-up-right article collection on the Cerby Help Center.

Important: You can only retrieve secrets to which you have the Owner role. Your permissions are determined by your API key based on Cerby’s RBAC system.

List secrets

get

With a GET request to the /secrets endpoint, you can retrieve a list of all your secrets in your Cerby workspace.

Important: The API scope required to use this endpoint is: Read secrets.

Query parameters
page[number]integer · min: 1Optional

The page number to retrieve in the paginated result set.

Default: 1
page[size]integer · min: 1 · max: 100Optional

The number of items to return per page.

Default: 25
Responses
chevron-right
200

OK - The JSON array with the secret objects requested on the specified page.

application/json
get
/secrets

Create a secret

post

With a POST request to the /secrets endpoint, you can create a secret in your workspace.

Important: The API scopes required to use this endpoint are Read secrets and Write secrets.

Body
Responses
post
/secrets

Retrieve secret by ID

get

With a GET request to the /secrets/{id} endpoint, you can retrieve the information of a secret by providing its ID.

Important: The API scope required to use this endpoint is: Read secrets.

Path parameters
idstring · uuidRequired

The unique identifier of the secret.

Responses
chevron-right
200

OK - The JSON array with the secret objects requested on the specified page.

application/json
get
/secrets/{id}

Retrieve the teams or users of a secret

get

With a GET request to the /secrets/{id}/members/{memberType} endpoint, you can retrieve the list of users or teams with shared access to a secret by providing their member type.

Important: The API scope required to use this endpoint is Read secrets.

Path parameters
idstringRequired

The unique identifier of the secret.

memberTypestring · enumRequired

The member type you want to list. The possible values are users or teams.

Possible values:
Query parameters
page[number]integer · min: 1Optional

The page number to retrieve in a paginated list.

Default: 1
page[size]integer · max: 100Optional

The number of items to display per page.

Default: 25
Responses
chevron-right
200

OK - The JSON array with the secret objects requested on the specified page.

application/json
get
/secrets/{id}/members/{memberType}

Share a secret with a user or team

post

With a POST request to the /secrets/{id}/members/{memberType} endpoint, you can share a secret with a user or team by providing their member type.

Important: The API scope required is Write secrets.

Path parameters
idstringRequired

The unique identifier of the secret.

memberTypestring · enumRequired

The member type to which you want to share the secret. The possible values are users or teams.

Possible values:
Body
Responses
post
/secrets/{id}/members/{memberType}

Last updated