Skip to main content
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 or the agent prompt 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

Public API quickstart

Create OAuth credentials, exchange them for a token, and make your first API call in about 10 minutes.

API reference

Endpoint-level request and response details, generated from the Public API OpenAPI contract.

MCP setup

Enable the MCP feature, create grants, and control what AI assistants can access in your company.

Connect Claude

Add FITsociety MCP to Claude as a custom connector and authorize with OAuth.

Security

Company scoping, grant boundaries, consent flags, and how FITsociety protects member data.

Troubleshooting

Fix common MCP connection, authorization, and tool-availability problems.
  1. Follow the Quickstart to get working credentials and a first successful call.
  2. Read the 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 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.