Route Reference

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.

Families

• Authentication: 26 generated endpoint entries. Dashboard auth, Supabase Auth hooks, access checks, session helpers, and permission discovery.
• Access and Core Data: 56 generated endpoint entries. Generic data access helpers, profile records, uploads, image proxying, SPA contracts, and guarded test-run utilities.
• Admin and Organization: 34 generated endpoint entries. Partner administration, organization settings, notices, Discord administration, and trust-safety enforcement records.
• Registration and Attendees: 70 generated endpoint entries. Attendee registration, profiles, fursonas, reservations, waitlist, group registration, and affiliate rewards.
• Event Management: 140 generated endpoint entries. Event configuration, conditions, activities, HR, communications, analytics, Dealers Den, check-in, inventory, and POS-adjacent operations.
• Finance and Payments: 52 generated endpoint entries. Payment providers, account records, finance programs, settlement records, refunds, transfers, and upgrades.
• Social and Integrations: 51 generated endpoint entries. Discord, Telegram, social account linking, state tokens, member tags, roles, and ZEP access.
• EMS LAN Support: 2 generated endpoint entries. Hosted LAN release proxy behavior and release download support.
• Webhooks and Contact: 12 generated endpoint entries. Public contact form, Auth hooks, and public waitlist entrypoints.

Checkpoint list

1. Checkpoint 1 - Family selected: Use the product area that owns the record, not the UI page that happens to call it.
2. Checkpoint 2 - Endpoint found: If the endpoint is missing from generated inventory, regenerate docs or inspect dynamic route code.
3. Checkpoint 3 - Contract reviewed: Do not rely on method and path alone. Auth, inputs, outputs, errors, and side effects matter.