KinesteX

Content APIs (Updated)

The Content API serves the KinesteX catalog: exercises, workouts, and multi-week plans. Every endpoint is a plain REST GET, authenticated with your company API key, paginated, filterable, and localized.


Use it to build your own content browser, a workout picker, a plan catalog, or to feed content into your own AI agent.


Base URL: https://data.kinestex.com


If KinesteX provisioned a dedicated domain for your company (a white-labeled host or a custom CDN), swap the host only. Paths, parameters, and payloads are identical.

Endpoints:


EndpointReturns
GET /api/exercises/clientPaginated exercise list
GET /api/exercises/client/{id}One exercise, by numeric ID or title
GET /api/workouts/clientPaginated workout list
GET /api/workouts/client/{id}One workout with its full exercise sequence
GET /api/plans/clientPaginated plan list
GET /api/plans/client/{id}One plan with weeks, days, and the current workout

Quick start:


bash
1curl "https://data.kinestex.com/api/exercises/client?body_parts=Chest&difficulty_level=easy&limit=5" \
2  -H "x-api-key: YOUR_API_KEY" \
3  -H "Language: en"

What changed since the legacy Content API (still documented here):


  • Server-side filtering on every list. search, body_parts, categories, difficulty_level, level, and translation_languages are applied in SQL, so you no longer fetch everything and filter on the client.
  • Real pagination. Offset paging with a complete pagination block (total, total_pages, has_next) instead of opaque cursor tokens.
  • Localization you can plan around. One language parameter for the whole response, plus translation_languages so you know which languages an item actually has.
  • One host. Content, the AI Trainer API, and workout sessions all live on data.kinestex.com.

Read Getting Started first (auth and language apply to every endpoint), then Filtering & Parameters for rules that hold across all three catalogs.