Environments and Bindings

Start With The Idea

Use this guide when a route, request, response, permission model, integration, or deployment behavior needs to be understood before people rely on it. In this guide, Environments and Bindings narrows that work to worker bindings, secrets, sandbox review variables, and external systems used by partners-api. Because this is a foundations page, read it as part of the Platform adoption learning path rather than as an isolated checklist.

An API is a contract between systems. Even technical changes can affect attendee records, dashboard behavior, notifications, payments, files, or staff tools. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What This Page Explains

This is the concept layer. Read it before trying to operate the workflow so the later steps make sense in ordinary language first. The intended readers are partner administrators, event leads, adoption leads, and integration owners. If the guide names a dashboard screen, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: partners-api.
• Records or contracts involved: API service expectations, Auth state, and Platform records.
• Main care point: Watch for using a service route with the wrong actor, changing a response another app depends on, leaking a secret, or triggering the same side effect twice.
• Proof worth keeping: route inventory, method and path, auth model, request and response shape, platform owner confirmation, test result, consumer note, and deployment evidence.

How The Idea Builds Toward Action

1. Say the idea in ordinary words: Begin by naming the Platform adoption situation, the owner, and the exact item involved in Environments and Bindings.
2. Connect the idea to one real screen or source: Use partners-api to connect the words on the page to the screen, file, route, or service trail that people actually use.
3. Name what could change for people or records: Keep API service expectations, Auth state, and Platform records in view so the work stays tied to the records or contracts it can affect.
4. Choose the next practical guide from the related links: Before handing off, save proof such as route inventory, method and path, auth model, request and response shape, platform owner confirmation, test result, consumer note, and deployment evidence so an adoption lead and a non-specialist reviewer can understand what the route does and how it was verified.

You Are Ready To Continue When

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on callers, records, permissions, secrets, side effects, and downstream apps.
3. Proof is findable: The handoff points to evidence that an adoption lead and a non-specialist reviewer can understand what the route does and how it was verified.

End-to-end adoption runbook

1. Step 1 - Name the API workflow and owner: Identify the product area, organization owner, service path, and relying team before adopting a workflow or integration.
2. Step 2 - Read the contract in human terms: Check who can use it, what information is exchanged, what can fail, what records change, and what proof the adopting team must keep.
3. Step 3 - Prepare auth and input deliberately: Confirm the right role, account, partner, event, and approved data before depending on the workflow.
4. Step 4 - Use or request the route in the right environment: Use the approved dashboard, rego, LAN, or integration environment and keep credentials out of notes, screenshots, and exports.
5. Step 5 - Check returned data and real side effects: Confirm the visible result, affected records, external action, and review evidence in plain language.
6. Step 6 - Record tests, docs, and handoff notes: Record the owner, expected behavior, adoption evidence, and escalation path before relying on it in production.

Binding groups

1. Action 1 - Core database: SUPABASE_URL, SUPABASE_ANON_KEY, SUPABASE_SECRET_KEY, SUPABASE_SERVICE_ROLE_KEY, and SUPABASE_JWT_SECRET.
2. Action 2 - Origins and apps: ALLOWED_ORIGIN, DASHBOARD_URL, SITE_URL, and REGO_URL.
3. Action 3 - CMS and media: CMS_GATE_SECRET, CMS_JWT_SECRET, CMS_TOKENS, SANITY_MEDIA_PROJECT_ID, SANITY_MEDIA_DATASET, SANITY_MEDIA_TOKEN, SANITY_PROJECT_ID, and SANITY_API_TOKEN.
4. Action 4 - Mail and hooks: CONTACT_TO_EMAIL, CONTACT_FROM_EMAIL, FPH_SUPPORT_EMAIL, GAS_EMAIL_WEBHOOK_URL, GAS_EMAIL_WEBHOOK_SECRET, and SUPABASE_AUTH_HOOK_SECRET.
5. Action 5 - Internal controls: CRON_SECRET, TEST_CONTROL_SECRET, STRESS_TEST_SUPPRESS_SIDE_EFFECTS.
6. Action 6 - Integrations: Google Wallet, Discord, Telegram, social-link state, partner DB config encryption, and LAN release GitHub bindings.