[Documentation](https://fluxnative.app/docs) / Connect services

# API keys and secrets

Store server keys by name; the assistant sees only the name and a description, and delivers them to your backend's functions.

![API keys and secrets in Server: a Name such as OPENAI_API_KEY, the Value, what it is for, and Save secret](https://fluxnative.app/guide-media/secrets.e8c7cf85.webp)

Name the key as your server code reads it; the value is stored encrypted and never shown again.

## Steps

1. Create the key in the provider's dashboard.
2. Click **Server** › **API keys & secrets**.
3. Name it as your server code reads it, in UPPER\_SNAKE\_CASE such as `OPENAI_API_KEY`, and add a one-line description.
4. Paste the value and save. To rotate it, replace the entry.

Then ask for the call in a function, not in the app:

`Summarize notes with OpenAI in an Edge Function using OPENAI_API_KEY.`

## Good to know

- Secrets reach your code only as Supabase Edge Function secrets, in Firebase Secret Manager (Blaze plan) or as Cloudflare Worker secrets. They never go into the mobile app.
- The value is stored encrypted and never shown again, to you or the assistant.
- Up to 50 entries per project. A key and its separate organization ID are two entries.

**Warning:** With no Supabase, Firebase or Cloudflare connected, a saved key has nowhere to go. Connect one under **Server** › **Backend** first.

## Related

[Supabase](https://fluxnative.app/docs/supabase) · [Firebase](https://fluxnative.app/docs/firebase)

Previous: [Ads](https://fluxnative.app/docs/ads) · Next: [Native builds overview](https://fluxnative.app/docs/builds-overview)

---

Store server keys by name; the assistant sees only the name and a description, and delivers them to your backend's functions.

Page: https://fluxnative.app/docs/secrets