Rotating secrets - E2B Docs

Update a secret with Secret.update. Each successful update stores a new immutable version and makes it current. Version numbers increase and are never reused within the same secret, but failed updates can leave gaps.

import { Secret } from 'e2b'

const secret = await Secret.update('stripe_api_key', 'sk_live_new...')
console.log(secret.version) // 2

from e2b import Secret

secret = Secret.update("stripe_api_key", "sk_live_new...")
print(secret.version)  # 2

After the update succeeds, matching HTTPS requests whose secrets lookup starts afterward use the new current value. A request that already resolved the old value can still use it. You don’t need to restart the sandbox or update its network rules, and a paused sandbox uses the current value after it resumes. References always resolve the current version. The public API and SDKs do not support version pinning, reading older values, or rolling back to a previous version. To restore an earlier credential, supply that value again with Secret.update.