> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e2b.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Store secrets with E2B and inject them into outbound HTTPS requests outside the sandbox.

<Note>
  Secrets are currently in private beta.
  If you'd like access, please reach out to us at [support@e2b.dev](mailto:support@e2b.dev).
</Note>

Secrets let you store credentials such as API keys with E2B and reference them by name.
Rather than passing a key as an environment variable or baking it into a template, where any code running in the sandbox can read it, you store the value once and reference it in a network rule.
The egress proxy injects the real value into matching outbound HTTPS requests outside the sandbox. Your sandbox configuration contains only a reference to the secret.

Secret values are write-only through the management API: create and update accept the value, while responses, reads, lists, and API errors never return it. Manage secrets from your trusted application, keeping its E2B API key outside the sandbox. Secrets belong to the project associated with that key.

Only inject credentials into destinations you trust. The destination receives the value and could expose it in its response to the sandbox.

With the E2B SDK you can:

* [Create a secret.](/secrets/create)
* [Inject secrets into the sandbox's requests.](/secrets/inject)
* [Rotate secrets without restarting sandboxes.](/secrets/rotate)
* [Delete secrets.](/secrets/delete)
* [List secrets and read their metadata.](/secrets/list)

For short-lived tokens minted per sandbox instead of stored credentials, see [workload identity](/iam/workload-identity).