Capability Reference

Choose Your Starting Point

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, Capability Reference narrows that work to grouped index for every partners-api capability family. Because this is a capability reference 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 Section Helps You Decide

This is the map page. Start here when you know the general area but not the exact guide. The page should help you choose the next safe reading path before opening a dashboard screen, file, service route, or record. 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.

A Natural Way Through The Section

1. Name the situation in front of you: Begin by naming the Platform adoption situation, the owner, and the exact item involved in Capability Reference.
2. Match it to the closest guide group: Use partners-api to connect the words on the page to the screen, file, route, or service trail that people actually use.
3. Open one guide at a time: 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. Return here when the work changes shape: 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.

Leave This Page With A Direction

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.

Families

• Authentication: 24 generated capability entries. Dashboard auth, Supabase Auth hooks, access checks, session helpers, and permission discovery.
• Access and Core Data: 56 generated capability entries. Generic data access helpers, profile records, uploads, image proxying, SPA contracts, and guarded test-run utilities.
• Admin and Organization: 34 generated capability entries. Partner administration, organization settings, notices, Discord administration, and trust-safety enforcement records.
• Registration and Attendees: 58 generated capability entries. Attendee registration, profiles, fursonas, reservations, waitlist, group registration, and affiliate rewards.
• Event Management: 125 generated capability entries. Event configuration, conditions, activities, HR, communications, analytics, Dealers Den, check-in, inventory, and POS-adjacent operations.
• Finance and Payments: 44 generated capability entries. Payment providers, account records, finance programs, settlement records, refunds, transfers, and upgrades.
• Social and Integrations: 50 generated capability entries. Discord, Telegram, social account linking, state tokens, member tags, roles, and ZEP access.
• EMS LAN Support: 2 generated capability entries. Hosted LAN release proxy behavior and release download support.
• Webhooks and Contact: 12 generated capability 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 capability is missing from generated inventory, ask the platform owner to refresh the inventory or confirm dynamic routing.
3. Checkpoint 3 - Contract reviewed: Do not rely on method and path alone. Auth, inputs, outputs, errors, and side effects matter.