MoveTogether Fitness

MoveTogether Fitness API docs and developer resources

Public, unauthenticated discovery surfaces for agents and developers working with MoveTogether Fitness — the cross-wearable fitness competition app at movetogetherfitness.com. Everything here is an OpenAPI-described, rate-limit-signalled, versioned read endpoint. These endpoints expose product documentation and schemas only, never private user health data.

When to use this

Canonical MoveTogether Fitness resources

  1. MoveTogether Fitness llms.txt — brand brief for agents

    Curated product facts, scoring rules, pricing, developer resource index, and when-to-use guidance for AI crawlers. Also at /v1/llms.txt.

    https://movetogetherfitness.com/llms.txt

  2. MoveTogether Fitness OpenAPI 3.1 specification

    The full service description: unique operationIds, a typed response schema on every JSON operation, RFC 9457 ProblemDetails errors, and documented rate-limit and deprecation headers for LLM function calling.

    https://movetogetherfitness.com/v1/openapi.json

  3. MoveTogether Fitness MCP server (Streamable HTTP)

    Model Context Protocol server exposing product facts, pricing, the developer resource index, the versioning policy, and this OpenAPI document as callable tools. Speaks 2026-07-28 and every earlier published revision. No auth.

    https://movetogetherfitness.com/v1/mcp

  4. MoveTogether Fitness MCP server card

    Well-known discovery document for Claude, ChatGPT, and other MCP-capable clients: transport, supported revisions, capabilities, and tool names.

    https://movetogetherfitness.com/.well-known/mcp/server-card.json

  5. MoveTogether Fitness API catalog

    RFC 9727 linkset naming every public machine-readable resource on this domain, including the deprecation policy.

    https://movetogetherfitness.com/.well-known/api-catalog

  6. MoveTogether Fitness product facts (JSON)

    Typed product facts — platforms, wearables, scoring model, canonical URLs — for agents that want one fact without loading a schema first.

    https://movetogetherfitness.com/v1/product.json

  7. MoveTogether Fitness pricing facts (JSON)

    What Free includes and what Pro adds, as typed JSON. Amounts live on /pricing because store and web prices differ.

    https://movetogetherfitness.com/v1/pricing.json

  8. MoveTogether Fitness developer resource index (JSON)

    This page as machine-readable JSON: every resource by name, URL, and media type.

    https://movetogetherfitness.com/v1/developer-resources.json

  9. MoveTogether Fitness versioning and deprecation policy (JSON)

    The versioning contract, the deprecation signals, the minimum notice period, and every currently deprecated path with its sunset date.

    https://movetogetherfitness.com/v1/deprecation-policy.json

  10. MoveTogether Fitness CLI (movetogether-fitness-cli)

    Official Node CLI wrapping every endpoint on this page. Run it with npx — no install, no API key.

    https://movetogetherfitness.com/developers#cli

  11. MoveTogether Fitness Help Center and Docs MCP

    End-user documentation with its own llms.txt and MCP server for deep product how-tos.

    https://docs.movetogetherfitness.com/

  12. Contact MoveTogether Fitness

    In-app support chat, privacy mailbox, and press channels.

    https://movetogetherfitness.com/contact

MoveTogether Fitness CLI

movetogether-fitness-cli wraps every endpoint on this page. It needs no API key, has no dependencies, and prints JSON on stdout so it pipes straight into jq. Deprecation warnings and rate-limit errors go to stderr, so a pipeline stays clean.

npx movetogether-fitness-cli overview
npx movetogether-fitness-cli openapi > movetogether-openapi.json
npx movetogether-fitness-cli policy
npx movetogether-fitness-cli product | jq -r '.links.mcp'

MoveTogether Fitness API versioning and deprecation policy

Current major version: 1. Every MoveTogether Fitness discovery endpoint is served under a major-version path prefix (/v1/) and echoes API-Version: 1. Additive changes ship in place; breaking changes ship under a new prefix (/v2/) and never mutate /v1/.

What counts as a breaking change

How a deprecation is announced

Once a resource is deprecated it keeps responding for at least 180 days, and its Sunset date is never moved earlier.

Currently deprecated

Machine-readable version of this section: /v1/deprecation-policy.json. A deprecated resource responds for at least 180 days after it is announced.

curl -sI https://movetogetherfitness.com/openapi.json
# Deprecation: @1787356800
# Sunset: Sun, 22 Aug 2027 00:00:00 GMT
# Link: <https://movetogetherfitness.com/developers#versioning>; rel="deprecation"; type="text/html", <https://movetogetherfitness.com/v1/openapi.json>; rel="successor-version"

Rate limits

Every response — success or error — carries the RateLimit header fields, in the Structured Fields syntax the IETF HTTP API rate-limit draft defines. The quota is 120 requests per 60 seconds per client. Exceeding it returns 429 with Retry-After and an RFC 9457 application/problem+json body.

curl -sI https://movetogetherfitness.com/v1/product.json
# RateLimit-Policy: "default";q=120;w=60
# RateLimit: "default";r=118;t=57
# API-Version: 1

Read r for requests remaining and t for seconds until the window resets.

Authentication

Public discovery endpoints (llms.txt, the OpenAPI document, the typed JSON documents, MCP, Markdown negotiation) require no API keys, tokens, or OAuth flow. The OpenAPI document declares an empty security array to say so explicitly. The mobile app uses Supabase JWT auth through Edge Functions for private user data — that surface is not part of this public schema. Agents must not attempt to scrape authenticated app APIs from the marketing domain.

Webhooks

MoveTogether Fitness does not expose inbound webhooks on the public marketing site, which is why the OpenAPI document declares no webhooks object. Subscription and payment webhooks (RevenueCat, Stripe) are server-to-server only and are not available to third parties. For integration questions contact support@movetogetherfitness.com.

Errors

Non-MCP endpoints return RFC 9457 application/problem+json matching the ProblemDetails schema, with a stable code field. MCP endpoints return JSON-RPC error envelopes; -32020 means a mirrored header disagreed with the body and -32022 means the requested protocol revision is not supported (the error data lists the ones that are).

Markdown content negotiation

Canonical HTML pages also serve text/markdown when the request Accept header prefers it (acceptmarkdown.com). Responses include Vary: Accept. Try:

curl -sI -H "Accept: text/markdown" https://movetogetherfitness.com/
# Content-Type: text/markdown; charset=utf-8
# Vary: Accept

Every resource, one list

The same index this page renders, served as JSON at /v1/developer-resources.json:

← Back to MoveTogether Fitness