> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fitsociety.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Developer Docs

> Start here when integrating with FITsociety developer APIs.

FITsociety developer documentation is split into three integration surfaces:

* **Public API** — server-to-server REST integrations for clients, bookings,
  finance, progress, forms, reporting, and webhooks. Authenticated with OAuth
  client credentials and Bearer access tokens.
* **MCP** — AI-assistant access through controlled company-scoped tools. Use
  [Agent Setup](/mcp/agent-setup) or the
  [agent prompt](/mcp/agent-setup-prompt.md) to let an AI client configure
  itself. Authenticated with MCP API keys or MCP OAuth.
* **Access Devices** — QR gates, badge readers, and door-controller
  validation. Authenticated with dedicated access-device keys.

## Pick your path

<CardGroup cols={2}>
  <Card title="Public API quickstart" icon="rocket" href="/public-api/quickstart">
    Create OAuth credentials, exchange them for a token, and make your first
    API call in about 10 minutes.
  </Card>

  <Card title="API reference" icon="code" href="/api-reference/overview">
    Endpoint-level request and response details, generated from the Public API
    OpenAPI contract.
  </Card>

  <Card title="MCP setup" icon="wrench" href="/mcp/setup-for-coaches">
    Enable the MCP feature, create grants, and control what AI assistants can
    access in your company.
  </Card>

  <Card title="Connect Claude" icon="message-bot" href="/mcp/connect-claude">
    Add FITsociety MCP to Claude as a custom connector and authorize with
    OAuth.
  </Card>

  <Card title="Security" icon="shield-halved" href="/mcp/security-and-privacy">
    Company scoping, grant boundaries, consent flags, and how FITsociety
    protects member data.
  </Card>

  <Card title="Troubleshooting" icon="circle-question" href="/mcp/troubleshooting">
    Fix common MCP connection, authorization, and tool-availability problems.
  </Card>
</CardGroup>

## Recommended path

1. Follow the [Quickstart](/public-api/quickstart) to get working credentials
   and a first successful call.
2. Read the [Contracts](/public-api/contracts) page before writing production
   code. It defines response envelopes, validation behavior, idempotency,
   pagination, rate limits, and field stability.
3. Use the API Reference tab for endpoint-level request and response details.
4. Use the domain guides for extra validation rules, privacy notes, and
   business guardrails.

## Sections

* **Brand assets** provides [official logos, FIT icons and downloads](/brand-assets)
  for integration settings and directory listings.
* **Docs** contains conceptual guides, validation rules, output contracts, and
  product-specific integration notes.
* **API Reference** is generated from the Public API OpenAPI contract and is the
  source for endpoint-level method, path, parameter, request body, and response
  details.
* **MCP** documents the AI tool interface and keeps its grants, OAuth metadata,
  and runtime endpoint separate from the REST Public API.
* **Changelog** lists externally relevant developer API documentation and
  contract changes.

## Versioning

The current REST developer surface is `/public/v1`. Existing fields remain
stable for the lifetime of v1. New fields may be added in a backward-compatible
way, but sensitive or internal model fields are not automatically exposed just
because they exist in backend models.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.