Skip to main content
Secrets are credentials Fimo itself uses: webhook headers, schedule runs, and agents. Your site never receives them. For an API key your site’s code calls with, use a private variable. Open Settings → Advanced settings → Secrets. Only site members with Full Access can add, replace, or remove secrets. The page shows all readable environments together. Each row is one key and Environment pair, with the Environment shown as a badge, so you can compare Production, Preview, and custom Environments without switching a page-level filter. Fimo hides each value after you save it. Secrets in site settings

​
Add a secret

Choose Add secret, select the Environment it applies to, enter an uppercase key such as RESEND_API_KEY, then enter its value. Add the same key again when another Environment needs its own value. You will not be able to view the value again after saving it. Adding a site secret Use the row menu to replace a secret value or delete the secret. Replacing a value keeps the same key, so integrations can continue referring to it.
Secret keys cannot start with PUBLIC_, VITE_, NEXT_PUBLIC_, or NUXT_PUBLIC_. Those prefixes can expose values to browser code.

​
Use secrets in integrations

When configuring a webhook header, insert an existing secret into a value such as Bearer RESEND_API_KEY. The secret stays hidden in Studio and in delivery history. Developers and coding agents can manage the same secrets with fimo secrets.

Webhooks

Send site events to services that use your secrets.

CLI reference

Manage site secrets from a terminal or coding agent.