Furries PH Docs
Dashboard
Platform API docs

Reference

External Services

External systems that partners-api may call or protect behind server-side routes.

First created Last updated

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.

Service map

  1. Action 1 - Supabase: Primary database, Auth, and service-role operations.
  2. Action 2 - Sanity: CMS and media asset operations.
  3. Action 3 - Google Apps Script mail: Transactional and contact email delivery path.
  4. Action 4 - Google Wallet: Attendee pass class and object integration.
  5. Action 5 - Discord and Telegram: Social linking, role sync, and member tag behavior.
  6. Action 6 - Cloudflare KV: CMS token storage where configured.
  7. Action 7 - GitHub releases: EMS LAN release proxy reads release metadata and assets.
  8. Action 8 - Deploy hooks: Rego deploy hook integration where configured.

All docs