Developers

Build with Ascend.

We expose the open parts of our system — exercise + food databases, share-card renderer, mountain registry. No paywall for read-only. Auth keys free, rate-limited at 60 req/min.

Endpoints

Method	Path	Description	Auth	Status
GET	/api/v1/exercises	Open exercise library — paginated, taxonomy + muscle-group tags	API key (free)	planned
GET	/api/v1/exercises/:slug	Single exercise — form notes, muscle map, variations	API key (free)	planned
GET	/api/v1/foods	Open food + macro database — barcode lookup + search	API key (free)	planned
GET	/api/v1/foods/:barcode	Barcode → macros + ingredients	API key (free)	planned
GET	/api/v1/share-cards/:kind/:id.svg	Render a PR / mountain / league share card. Public IDs only.	none	beta
GET	/api/v1/mountains	Climbable mountain registry — slug, elevation, region, plan length	none	planned

Most endpoints are planned — gated on internal data-quality + rate-limit infrastructure. Subscribe via email below to be notified when stable.

Example — fetch an exercise

curl -H "Authorization: Bearer YOUR_KEY" \
  https://api.getascend.club/v1/exercises/barbell-back-squat

{
  "slug": "barbell-back-squat",
  "name": "Barbell Back Squat",
  "primary": ["quadriceps", "glutes"],
  "secondary": ["hamstrings", "core", "spinal-erectors"],
  "equipment": ["barbell", "squat-rack"],
  "form_notes": ["...", "..."],
  "variations": ["front-squat", "goblet-squat"]
}

Why open?

Most fitness apps lock their exercise + food databases inside the app. We think those are commodities — the value Ascend ships is the AI coach, mountain progression, anatomy heatmap, and gamification. Anyone should be able to build something useful with our taxonomy.

SDK + OSS

· @ascend/share-card-renderer — render PR / mountain / league SVG cards client-side (planned npm)
· @ascend/exercises-client — typed TS client for the exercises endpoint (planned)
· @ascend/anatomy-heatmap — React component, taxonomy-aware (planned)

Repo: github.com/samwilsonnz/AscendFitnessApp (private during pre-launch; OSS modules will live in a separate org).

Build something

Email [email protected] with what you want to ship. Early access keys go out monthly.