Skip to navigation

Secret Manager

Secret Manager is a safe place for the passwords, API keys, tokens and other sensitive values your applications need, so you don’t have to write them into code or config files. You save a value once; your app or script reads the current value when it needs it. Every change is kept as a new version, so you can see what changed and roll back.

Secret Manager is turned on per organization. If Secret Manager isn’t under Tools in your sidebar, contact support to request access.

When to use it

The value is…Keep it inWhy
A database password, a third-party API key, a signing keySecret ManagerKept out of code and Git, every change versioned, access controlled per app
An IBEE API token or S3 secret key you just createdSecret ManagerIBEE shows those once only; save the copy here
A setting that isn’t secret (a URL, a feature switch, a region name)Your app’s environment variables or config fileSecret Manager is for sensitive values
A login to a Linux VMSSH KeysVMs read SSH keys, not secrets

Terms

TermMeaning
StoreA folder for related secrets, for example Payments. Each store belongs to one workspace. Its store key (for example payments) is made from the name and never changes.
SecretA named set of key/value pairs inside a store, for example stripe-api holding API_KEY = sk_live_….
VersionA saved state of a secret. Every update adds a version; older ones stay until you destroy them.
AccessA sign-in for an application (not a person): AppRole for VMs, servers and scripts, or Kubernetes for pods. Each has Read only or Read & write permission on chosen stores.

How it works

  1. You create a store in a workspace.
  2. You add a secret with one or more key/value pairs.
  3. Your program reads the secret, either with a platform API token that has Secret Manager → Read, or with its own Access sign-in.
  4. When a value changes, you save a new version; the program gets the new value on its next read.

Before you begin

  • Role: to create or change anything you need write access to the workspace: the Owner, an Admin, or a Technical member. Collaborators can open Secret Manager read-only, which includes viewing secret values. Billing members have no access. See Team members & access roles.
  • Identity verification of your own account, to make changes. See Verify your identity.
  • Billing: creating a store or a secret goes through the billing check, so your wallet must allow new resources.
  • For the API: a platform API token with Secret Manager permission, and the workspace ID.

Create a store and a secret

1

Open Secret Manager

Open a workspace. In the sidebar, under Tools, click Secret Manager.

2

Create a store

Click Create Store. In Create store, enter a Store name such as Payments (1–128 characters) and an optional Description, then click Create store. The store appears in the list with its Store Key and the status Active.

3

Open the store

Click the store. It has two tabs: Secrets and Access.

4

Create a secret

On Secrets, click Create Secret. Enter a Secret name such as stripe-api: 2–64 characters, lowercase letters, digits and hyphens, starting with a letter or digit.

5

Add the values

Enter a key such as API_KEY and its value. Click + Add another key for more pairs. Click Create secret.

Verify it worked

The secret appears on the Secrets tab. Click View to see the current version’s values as JSON, with Copy JSON.

Read a secret from code

Any program with a platform API token can read a secret’s current value. The token needs Secret Manager → Read (secret-store.read), and every request must use the workspace that owns the store.

First find the store’s and the secret’s IDs, then read the value:

export IBEE_TOKEN="ibee_prod_key_xxxxxxxxxxxx.xxxxxxxx"
WS=907479 # your workspace ID
# 1. List stores; note the "id" of yours
curl "https://api.ibee.ai/v1/secret-store/stores?workspace_id=$WS" \
-H "Authorization: Bearer $IBEE_TOKEN"
# 2. List the store's secrets; note the secret's "id"
curl "https://api.ibee.ai/v1/secret-store/stores/STORE_ID/secrets?workspace_id=$WS" \
-H "Authorization: Bearer $IBEE_TOKEN"
# 3. Read the current value
curl "https://api.ibee.ai/v1/secret-store/secrets/SECRET_ID/value?workspace_id=$WS" \
-H "Authorization: Bearer $IBEE_TOKEN"

The last call returns the values under data:

{
"id": "secret_123",
"secret_name": "stripe-api",
"data": { "API_KEY": "sk_live_..." },
"metadata": { "version": 1, "created_time": "2026-10-30T09:00:00Z" }
}

Lists and metadata calls never include values; only the value and version calls do. To create a secret through the API, send POST /secret-store/stores/{store_id}/secrets with {"secret_name": "stripe-api", "value": {"API_KEY": "sk_live_..."}}. All operations are in the Secret Store API reference.

Change, roll back and delete secrets

Each secret’s row has these actions:

ActionWhat it does
ViewShows the current values as JSON, with Copy JSON
UpdateOpens the values to edit; Save new version replaces them all. A key you remove is gone from the new version.
HistoryLists every version and its state; Rollback copies an older version into a new current version
DeleteAsks “This will soft-delete …”; click Delete secret

Delete is a soft delete. The secret stays in the list with the status Soft Deleted, and its name stays taken. Through the API you can restore it (POST /secret-store/secrets/{secret_id}/undelete), or remove it for good (DELETE /secret-store/secrets/{secret_id}/permanent). Permanent delete and destroying versions can’t be undone.

Give an application its own access

An Access entry lets a program sign in to Secret Manager with its own credentials instead of your API token.

1

Create the access

On the store’s Access tab, click Create Access. Choose the Access method (AppRole or Kubernetes), enter an Access name such as payments-api (unique in the workspace), and choose the Permission: Read only or Read & write. For Kubernetes, also enter the Kubernetes namespace and Service account. Click Create access.

2

Get the sign-in details

Click Login Details. AppRole shows the Role ID, a Secret ID and its Secret ID accessor. Kubernetes shows the Role name, Kubernetes namespace and Service account.

3

Give the program its details

Store the Role ID and Secret ID where the program can read them at start-up, such as its environment. The program signs in and receives a session token that lasts up to 1 hour, then signs in again.

Every time you open Login Details for an AppRole access, IBEE creates a new Secret ID, and earlier Secret IDs keep working. Rotate secret ID also adds a new one without cancelling the old ones. To cut off a leaked Secret ID, Delete the access and create a new one.

Other actions on an access:

  • Permissions: shows Current permissions. Under Add permission, pick a Store and a Permission, and tick Can read older versions (on by default), Can roll back or Can permanently destroy versions (the last needs Read & write). A Read only access can’t be given write, roll back or destroy later.
  • Revoke sessions: ends the access’s current sessions; it can sign in again.
  • Disable / Enable: blocks the access without deleting it, and ends its sessions.
  • Delete: confirm Delete access. It removes the access everywhere, including its permissions on other stores.

Archive or delete a store

From the store’s Actions menu:

  • Archive (confirm Archive): applications can no longer read from the store and nothing in it can be changed. The store stays in the list with the status Archived. Its secrets still count for billing. Restore brings it back.
  • Delete (type the store’s name, then Delete permanently): removes the store and all its secrets. This can’t be undone. Accesses that also use other stores are kept; only this store’s permission is removed.

Deleting a store deletes every secret in it, permanently. Copy any value you still need first, or Archive the store instead.

Limits and billing

Value
Store name1–128 characters, unique in the workspace
Store keyUp to 64 characters, made from the name; never changes
Secret name2–64 characters: a-z, 0-9 and -, starting with a letter or digit; unique in the store
Secrets per batch create (API)Up to 500
Stores and secrets per planNo plan limit
App session tokenUp to 1 hour
AppRole Secret IDNo expiry and no use limit
Shown in the portalThe first 100 stores, and the first 100 secrets in a store
BilledEach active secret, and secret reads in units of 10,000. Stores aren’t charged. Secrets in an archived store still count.

Your usage appears under Billing → Usage. See Billing and usage.

Security tips

  • Give each application its own Access with Read only permission on only the stores it needs.
  • Use separate stores for production and test values, ideally in separate workspaces.
  • Collaborators can view values. Invite people who shouldn’t see secrets with a role that has no access to the workspace.
  • Never log secret values or Secret IDs.
  • If a value leaks, change it at its source (for example, rotate the database password), then Update the secret.

Troubleshooting

API errors come back as JSON with an error code and message.

You seeWhat it meansWhat to do
409 “Store with name ’…’ already exists” (portal: “Store already exists”)A store with that name is in the workspaceUse the existing store, or another name
409 “Secret ’…’ already exists in store ’…’”The name is taken, possibly by a soft-deleted secretPick another name, or permanently delete the old secret through the API
”secret_name must match [a-z0-9][a-z0-9-]{1,63} …”Uppercase, _ or another character, or the wrong lengthUse 2–64 lowercase letters, digits and hyphens
403 FORBIDDEN “Secret ’…’ does not belong to workspace ’…’”The workspace_id isn’t the one that owns the secretUse the workspace that owns the store
403 insufficient_scope with required_scope secret-store.read or secret-store.writeThe API token lacks Secret Manager permissionCreate a token with Secret Manager → Read (or Edit)
409 STORE_ARCHIVED “Store ’…’ is archived. Unarchive it first.”You tried to change an archived storeRestore the store first
403 “Identity is disabled”The access is disabledEnable it
403 verification_requiredYour account isn’t identity-verifiedComplete verification
402 “Billing does not allow new resources for this organization right now.”The billing check refused the createSee Billing admission checks
403 product_not_enabledSecret Manager isn’t enabled for your organizationContact support