Secrets and Environment Variables

End-to-end developer runbook

1. Step 1 - Confirm the API area: Identify the product area, route module, endpoint path, and consumer before writing or calling code.
2. Step 2 - Read the endpoint contract: Check method, auth, parameters, response, errors, side effects, and related docs.
3. Step 3 - Prepare authentication and input: Use the right session, bearer token, webhook secret, or internal header. Validate body and query data before sending it.
4. Step 4 - Make the request: Call the endpoint from the correct origin and environment. Keep credentials and secrets out of logs.
5. Step 5 - Verify response, side effects, and records: Confirm status code, response shape, database records, external side effects, and audit evidence.
6. Step 6 - Add tests, docs, and handoff notes: Update route inventory, consumer notes, and certification checks before depending on the change.

Secret workflow

1. Action 1 - Name the binding: Document the environment variable name and purpose.
2. Action 2 - Classify the secret: Database, auth, mail, social, wallet, LAN release, cron, test, encryption, or CMS.
3. Action 3 - Identify routes that use it: Link route reference pages and source modules.
4. Action 4 - Define local setup: Explain how a developer obtains a safe development value without exposing production.
5. Action 5 - Verify deployment binding: Check Wrangler and Cloudflare environment configuration before release.