LegitFit · OAuth Scopes

LegitFit OAuth Scopes

OAuth 2.0 searched

LegitFit publishes 2 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the LegitFit API on a user’s behalf.

Tokens are issued from https://legitfit.com/api/oauth2/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyFitnessGym ManagementStudio ManagementSchedulingMembershipsPaymentsSoftware-as-a-ServiceMCPIreland

Scopes: 2 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://legitfit.com/api/oauth2/authorize

Token URL
https://legitfit.com/api/oauth2/token

Flows
authorizationCode

Scopes (2)

Scope	Description	Flows
mcp:read	Read access to the LegitFit MCP server at https://legitfit.com/api/mcp.	authorizationCode
mcp:write	Write access to the LegitFit MCP server at https://legitfit.com/api/mcp.	authorizationCode

📄 Provider scope reference: https://legitfit.com/.well-known/oauth-protected-resource

Source

OAuth Scopes

generated: '2026-07-19'
method: searched
source: https://legitfit.com/.well-known/oauth-authorization-server
docs: https://legitfit.com/.well-known/oauth-protected-resource
note: >-
  LegitFit publishes no OpenAPI, so these scopes were read directly from the
  RFC 8414 authorization-server metadata and the RFC 9728 protected-resource
  metadata. Both documents advertise the same two scopes, which gate the MCP
  server at https://legitfit.com/api/mcp. LegitFit publishes no human-readable
  scope reference page; the descriptions below restate the scope names and the
  resource they protect, and no finer-grained permission mapping is asserted.
schemes:
- name: LegitFitOAuth2
  source: well-known/legitfit-oauth-authorization-server.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://legitfit.com/api/oauth2/authorize
    tokenUrl: https://legitfit.com/api/oauth2/token
scopes:
- scope: mcp:read
  description: Read access to the LegitFit MCP server at https://legitfit.com/api/mcp.
  flows:
  - authorizationCode
  resources:
  - https://legitfit.com/api/mcp
  sources:
  - well-known/legitfit-oauth-authorization-server.json
  - well-known/legitfit-oauth-protected-resource.json
- scope: mcp:write
  description: Write access to the LegitFit MCP server at https://legitfit.com/api/mcp.
  flows:
  - authorizationCode
  resources:
  - https://legitfit.com/api/mcp
  sources:
  - well-known/legitfit-oauth-authorization-server.json
  - well-known/legitfit-oauth-protected-resource.json

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/legitfit-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.