{"slug":"secrets","title":"API keys and secrets","summary":"The vault holds backend keys by name. The assistant sees the name and a one-line description, never the value, and delivers secrets to your backend.","body":"Open Connections, then **API keys & secrets**. Use it for any server-side key: an AI provider, an email sender, a payment provider, or a webhook signing secret.\n\n## Add an entry\n\n1. Create the key in the provider's dashboard.\n2. Name it the way your server code reads it, in UPPER_SNAKE_CASE, for example `OPENAI_API_KEY`.\n3. Add one line saying what it is for.\n4. Paste the value and save.\n\nA key and a separate organization ID are two entries. A project can hold up to 50.\n\nThe value is stored encrypted and is not shown again, not in the builder and not to the assistant. To rotate a key, replace the entry.\n\n## How it reaches your code\n\nNamed secrets are pushed into the backend you connected, such as Supabase Edge Function secrets or Firebase Secret Manager. They are not written into the mobile app.\n\n> [!TIP]\n> Ask the assistant to call the provider from a function, not from the app. For example: \"Summarize notes with OpenAI in an Edge Function using OPENAI_API_KEY.\"","sectionSlug":"connect","sectionTitle":"Connect services","updatedAt":"2026-09-23T22:51:25.250Z","previous":{"slug":"in-app-purchases","title":"In-app purchases"},"next":{"slug":"builds-overview","title":"Native builds overview"}}