Skip to main content
TheFitnessDB

The exercise API roadmap for product teams

TheFitnessDB is building an exercise data API for product teams that need structured anatomy, equipment, and safety context. Join the waitlist to follow early access.

Join WaitlistView Pricing
Waitlist openPlanned API shapeSecurity-first launch

Why Fitness Databases Fail Your Users

Data Incomplete

Most exercise APIs lack anatomical depth. No ligament data, no nerve pathways, no clinical safety flags.

Integrations Are Slow

Off-the-shelf fitness databases are bloated. Building your own anatomical dataset is a 6-month project.

No Medical Context

Your users have injuries and contraindications. A generic database can't help you suggest safe alternatives.

What we're planning to ship first

The early API direction centers on structured exercise data with enough context for real product workflows.

  • Muscles

    Primary, secondary, and stabilizer relationships are part of the planned data model.

  • Ligaments & Joints

    Joint context and ligament-related fields are in scope for the early API design.

  • Nerves & Innervation

    Nerve and innervation coverage are on the roadmap, with schema details still being finalized.

  • ICD-10 Contraindications

    Condition and safety context are planned before public access opens.

{
  "slug": "barbell-back-squat",
  "name": "Barbell Back Squat",
  "primaryMuscles": [
    "quadriceps-rectus-femoris",
    "gluteus-maximus"
  ],
  "ligamentLoads": [
    {
      "slug": "anterior-cruciate-ligament",
      "stressLevel": 0.72
    },
    {
      "slug": "medial-collateral-ligament",
      "stressLevel": 0.45
    }
  ],
  "nerveInvolvement": [
    "femoral-nerve",
    "sciatic-nerve"
  ],
  "contraindications": [
    {
      "icd10Code": "M17.1",
      "condition": "Unilateral primary osteoarthritis of knee",
      "severity": "relative"
    }
  ]
}

Preview the planned request shape

These samples show the API direction, not a public endpoint you can call today.

JavaScript
// Preview of the planned request shape
const response = await fetch(
  'https://api.thefitnessdb.com/v1/exercises/barbell-back-squat',
  { headers: { 'Authorization': 'Bearer YOUR_API_KEY' } }
);
const exercise = await response.json();
Response
{
  "slug": "barbell-back-squat",
  "name": "Barbell Back Squat",
  "difficulty": "intermediate",
  "primaryMuscles": ["quadriceps-rectus-femoris", "gluteus-maximus"],
  "secondaryMuscles": ["hamstrings-biceps-femoris", "erector-spinae"],
  "equipment": ["barbell", "squat-rack"],
  "contraindications": [
    { "icd10Code": "M17.1", "severity": "relative" }
  ]
}
Join Waitlist

Launch status

What is already decided and what is still being finalized before public access.

OpenAPI 3.1 SpecPlanned
TypeScript TypesPlanned
Official SDKsRoadmap
Rate LimitsNot published yet
WebhooksRoadmap
Breaking ChangesPolicy planned

Questions from Developers

The first public schema is being shaped around exercise structure, anatomy, equipment, and safety context. We'll publish the exact launch scope before early access opens.

Health checks and reliability targets are part of launch planning. We'll publish uptime commitments together with the public API tiers, not before.

The support model will be published with the launch tiers. Early-access updates will explain what documentation, email support, and response targets are included.

Rate limits and burst behavior are not published yet. We'll document them before the first sandbox release.

Bulk export policy has not been finalized yet. Early-access documentation will explain what is API-only and what may be exportable later.

The current direction is privacy-conscious, GDPR-aware infrastructure. Any formal audit or certification claims will be published only once they are actually in place.

Follow the API launch

Join the waitlist to see the first developer releases, pricing updates, and early-access onboarding details.

Join WaitlistView Pricing