A technical guide to shipping workout content, personalization, video delivery, and insights with the Hyperhuman Content API

Most teams do not want to build a fitness content stack from scratch.

They want to ship.

They need workouts, programs, exercise videos, metadata, playlists, streams, personalization, session tracking, feedback, insights, and delivery across app, web, embeds, API, and social.

That is what the Hyperhuman Content API is built for.

One API.

Delivery.
Personalization.
Insights.
Growth loops.

Fitness content infrastructure for health, wellness, and fitness products.

What You Can Build

Hyperhuman helps product and engineering teams launch modern fitness, wellness, and digital health experiences faster.

Product Goal What You Can Ship API / Platform Layer
Launch a content catalog Browse workouts, programs, exercises, metadata, streams Publish Content
Add personalization Recommend the next best workout or plan AI Recommend
Generate new sessions Create workouts and programs from profile, goal, equipment, and duration AI Generate
Adapt over time Evolve existing workouts and programs as users progress AI Adapt
Close the feedback loop Track sessions, feedback, Daily Digest, and pillar insights AI Insights
Move faster on web Embed players, workout pages, and library grids Embed & Go
Build your own UX Use playlists, segments, HLS streams, and metadata Custom Player
Support global users Localized metadata, audio, overlays, and content surfaces Localization
Manage users Invite, suspend, reactivate, remove, and map end users End-user Lifecycle
Grow content ops Social Drops, Content Autopilot, and publishing workflows Automation

Useful links:

Who This Is For

This guide is built for teams shipping digital health, wellness, and fitness products.

Team Use Case
Fitness apps Add personalized workouts, programs, streams, and insights
Wellness platforms Deliver guided movement, recovery, and habit journeys
Corporate wellness providers Embed wellness sessions into portals or apps
Gym chains Launch hybrid in-club and at-home member journeys
Weight management platforms Add movement plans, logbooks, and adaptive sessions
Physio / rehab platforms Deliver structured exercise content and adherence loops
Connected hardware brands Power guided training around equipment
Developer teams Build custom players, app integrations, and content workflows
AI product teams Use OpenAPI, LLM bundles, and agent guides for faster implementation

The Core Idea

Do not build the whole stack.

Plug into the layer that already exists.

Hyperhuman gives you:

  • AI-ready workout and exercise content
  • Structured workout and program data
  • HLS playlists and streamable media
  • Full video and audio exports
  • AI recommendations
  • AI workout and plan generation
  • AI adaptation
  • Daily Digest and 360 insights
  • Session tracking and feedback loops
  • End-user lifecycle management
  • Localization
  • Embeds and custom player support
  • Automation and social publishing surfaces

You bring:

  • Your app
  • Your users
  • Your product logic
  • Your brand
  • Your business model

Architecture Overview

A typical Hyperhuman API integration has five layers.

Layer Your System Hyperhuman
Client app Mobile app, web app, portal, connected hardware UI Player, streams, metadata, workouts, programs
Backend User auth, entitlements, business rules, profile storage Content API, org library, personalization endpoints
Content layer Product surfaces and discovery UX Smart Library, workouts, programs, exercise assets
Intelligence layer User context, goals, lifecycle triggers Recommend, Generate, Adapt, Insights
Operations layer Admin tools, content planning, marketing Teams workspace, automation, Social Drops, analytics

Recommended flow

Your Client App
    ↓
Your Backend
    ↓
Hyperhuman Content API
    ↓
Workouts / Programs / Playlists / Streams / AI
    ↓
Session Tracking + Feedback
    ↓
Insights + Recommendations + Adaptation

Production rule

Keep API keys on your backend.

Your frontend should call your backend.
Your backend should call Hyperhuman.

That gives you better control over access, quotas, entitlements, logging, and security.

The Five API Capabilities

The API stacks five product capabilities on the same content library.

Capability Main Job Best For Docs
Publish Content List, filter, play, stream workouts and programs MVP, catalog, CMS, VOD, app content Workouts, Plans
AI Recommend Rank existing content for a user Fast “Next Up” experiences AI Recommendation
AI Generate Create new workouts or multi-week plans Highly personalized sessions AI Generation
AI Adapt Modify existing workouts or plans Progression, deload, substitutions AI Adaptation
AI Insights Turn usage and feedback into guidance Retention, re-engagement, Daily Digest AI Insights

Key API Basics

Area Current Pattern
Base URL https://content.api.hyperhuman.cc
Auth X-Api-Key: YOUR_API_KEY
API docs Docs Introduction
Spec OpenAPI JSON / OpenAPI YAML
Pagination offset + limit or links.next, depending on endpoint
IDs Opaque IDs; do not parse or infer structure
Localization Pass locale, for example fr-FR
Heavy endpoints Recommend, Generate, Adapt, Insights, Chat, full exports, and video generation may carry higher rate-limit weight
AI implementation resources LLM Bundle, Agent Guide

Integration Path: Pick Your Build Mode

You can integrate at three levels.

Path Build Effort Best For What You Control
Embed & Go Low Portals, MVPs, corporate wellness, landing pages Page placement, access, campaign flow
Stream / Export Medium VOD, CMS, offline playback, audio delivery Playback wrapper, distribution logic
Custom Player High Mobile apps, connected hardware, premium UX Full UI, playlist rendering, analytics, progression

Useful docs:

Delivery Options

Delivery Mode What You Get Best Use Case
Embedded workout player Hosted player in an iframe Fastest path to live playback
Embedded library pages Hosted workout or program grids Portals, member web, MVPs
Playlist + HLS Ordered segments and streams Custom mobile/web player
Full video export Complete workout video URL VOD, CMS, downloads, simple playback
Audio export Complete audio-guided workout Low bandwidth, audio-first experiences
Workout JSON receiver Generated workout rendered in hosted player Generate → instantly play
API-only integration Full data and media control Custom apps and connected hardware

5-Day API Launch Plan

This is the fastest practical path for a technical team.

Day 1: Connect and Fetch Content

Goal: show real content in your product.

Task Endpoint
Get workout categories and difficulties GET /v1/workouts/metadata
Get equipment metadata GET /v1/workouts/equipment/metadata
Get exercise metadata GET /v1/workouts/exercises/metadata
List organization workouts GET /v1/orgs/{orgId}/workouts
List organization plans GET /v1/orgs/{orgId}/plans
Get organization settings GET /v1/orgs/{orgId}/metadata

Outcome:

Your app can display real workouts, programs, categories, filters, equipment, difficulty, and metadata.

Docs:

Day 2: Build Playback

Goal: deliver a guided workout experience.

Task Endpoint
Get workout details GET /v1/workouts/{workoutId}
Get playlist segments GET /v1/workouts/{workoutId}/playlist
Get full video export GET /v1/workouts/{workoutId}/export/video/stream_url
Get audio export GET /v1/workouts/{workoutId}/export/audio/stream_url
Get workout music GET /v1/workouts/{workoutId}/music

Outcome:

You can ship either a hosted player, a simple stream, or a fully custom player.

Docs:

Day 3: Capture User Context

Goal: personalize without guessing.

Store or pass user context such as:

  • Age
  • Gender
  • Fitness level
  • Goals
  • Available equipment
  • Training days per week
  • Preferred duration
  • Feedback
  • Session history
  • External user ID
  • Email or internal user ID

Outcome:

Your app understands the user before it recommends, generates, or adapts content.

Docs:

Day 4: Add Personalization

Goal: make the experience feel built around the user.

Personalization Need Endpoint
Recommend workouts POST /v1/orgs/{orgId}/workouts/recommend
Recommend plans POST /v1/orgs/{orgId}/plans/recommend
Generate workouts POST /v1/orgs/{orgId}/workouts/generate
Generate plans POST /v1/orgs/{orgId}/plans/generate
Adapt workouts POST /v1/orgs/{orgId}/workouts/{workoutId}/adapt
Adapt plans POST /v1/orgs/{orgId}/plans/{planId}/adapt

Outcome:

Users open your product and see the right next workout or plan.

Docs:

Day 5: Track, Learn, Improve

Goal: close the loop.

Task Endpoint
Start a workout session POST /v1/workouts/{workoutId}/sessions/start
Update progress PATCH /v1/workouts/{workoutId}/sessions/{sessionId}
End or complete session POST /v1/workouts/{workoutId}/sessions/end / complete
Submit feedback POST /v1/workouts/{workoutId}/feedback
Fetch feedback options GET /v1/workouts/feedback/options
Monitor org usage GET /v1/orgs/{orgId}/stats
Fetch Daily Digest GET /v1/orgs/{orgId}/endusers/{endUserId}/insights/digest
Fetch pillar details GET /v1/orgs/{orgId}/endusers/{endUserId}/insights/pillars/{pillarType}

Outcome:

Your product can learn from real usage and use those signals to drive retention.

Docs:

Recommend vs Generate vs Adapt

This is the most important product decision.

Scenario Use Recommend Use Generate Use Adapt
User opens app and needs instant options Yes No No
You already have a strong content library Yes Sometimes Yes
You need a fully custom workout No Yes Sometimes
You want to preserve an existing workout’s intent No No Yes
You need the fastest response Yes No No
You need exact duration, equipment, or goal constraints Sometimes Yes Yes
You want to reduce AI cost and latency Yes No Sometimes
User missed sessions or gave feedback Sometimes Sometimes Yes
You need a multi-week plan Yes, for existing plans Yes, for new plans Yes, for progression

Simple decision framework

Use Recommend when speed matters.
Use Generate when personalization matters most.
Use Adapt when continuity matters.

Most mature products use all three.

Example: First Request

curl -X GET 'https://content.api.hyperhuman.cc/v1/workouts/metadata' \
  -H 'X-Api-Key: YOUR_API_KEY'

Use this to populate:

  • Workout categories
  • Difficulty filters
  • Generation inputs
  • Discovery UI

Docs:

Example: Generate a Workout

curl -X POST 'https://content.api.hyperhuman.cc/v1/orgs/{organizationId}/workouts/generate' \
  -H 'X-Api-Key: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "endUserProfileDetails": {
      "age": 28,
      "fitnessLevels": ["beginner"],
      "trainingDaysPerWeek": 3
    },
    "exerciseSources": ["premium_stock"],
    "durationOptions": {
      "minMinutes": 20,
      "maxMinutes": 20
    },
    "categoryId": "615aa3f0dbe7140012c59e94"
  }'

Use this when you need a fresh session built around user constraints.

Docs:

Example: Recommend From Library

curl -X POST 'https://content.api.hyperhuman.cc/v1/orgs/{organizationId}/workouts/recommend' \
  -H 'X-Api-Key: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "endUserProfileDetails": {
      "age": 32,
      "fitnessLevels": ["intermediate"],
      "trainingDaysPerWeek": 4
    },
    "durationOptions": {
      "minMinutes": 20,
      "maxMinutes": 30
    }
  }'

Use this when you have existing workouts and want a fast, ranked “Next Up” experience.

Docs:

Example: Adapt an Existing Workout

curl -X POST 'https://content.api.hyperhuman.cc/v1/orgs/{organizationId}/workouts/{workoutId}/adapt' \
  -H 'X-Api-Key: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "endUserProfileDetails": {
      "age": 34,
      "fitnessLevels": ["intermediate"],
      "trainingDaysPerWeek": 3
    },
    "exerciseSources": ["premium_stock", "team_exercises"],
    "userGuidance": "Limited time today. Prefer a lower-impact version with shorter duration."
  }'

Use this when you want to preserve the workout’s original purpose while adjusting the session to the user’s current context.

Docs:

Example: Fetch a Daily Digest

curl -X GET 'https://content.api.hyperhuman.cc/v1/orgs/{organizationId}/endusers/{endUserId}/insights/digest?date=2026-01-10' \
  -H 'X-Api-Key: YOUR_API_KEY'

Use this to power:

  • Today view
  • Readiness cards
  • Training recommendations
  • Re-engagement nudges
  • Health, training, recovery, movement, nutrition, and body insight surfaces

Docs:

End-User Lifecycle

For B2B products, user governance matters.

Need Endpoint
List users GET /v1/orgs/{orgId}/endusers
Find user GET /v1/orgs/{orgId}/endusers/find
Invite users POST /v1/orgs/{orgId}/endusers/invite
Suspend access PUT /v1/orgs/{orgId}/endusers/suspend
Reactivate access PUT /v1/orgs/{orgId}/endusers/reactivate
Remove user DELETE /v1/orgs/{orgId}/endusers

Use this when you need:

  • Enterprise provisioning
  • Client account management
  • Subscription-based access
  • B2B customer workspaces
  • User suspension / reactivation
  • Clean lifecycle control

Docs:

Plans and Program Flows

Workouts solve today.

Plans solve the journey.

Product Need Endpoint
List organization plans GET /v1/orgs/{orgId}/plans
Get plan details GET /v1/plans/{planId}
Get plan workouts GET /v1/plans/{planId}/workouts
Recommend plans POST /v1/orgs/{orgId}/plans/recommend
Generate plans POST /v1/orgs/{orgId}/plans/generate
Adapt plans POST /v1/orgs/{orgId}/plans/{planId}/adapt
Start plan for user POST /v1/orgs/{orgId}/endusers/{endUserId}/plans/start
Get active plan GET /v1/orgs/{orgId}/endusers/{endUserId}/plans/active
Track active plan progress GET /v1/orgs/{orgId}/endusers/{endUserId}/plans/active/progress

Use plans when you need:

  • Multi-week programs
  • Onboarding journeys
  • Goal-based plans
  • Adherence tracking
  • Progression
  • Retention loops

Docs:

Localization

Global products need native experiences.

Pass locale to fetch localized content where supported.

curl -X GET 'https://content.api.hyperhuman.cc/v1/workouts/{workoutId}?locale=fr-FR' \
  -H 'X-Api-Key: YOUR_API_KEY'

Localization can support:

  • Workout names
  • Exercise names
  • Equipment names
  • Muscle groups
  • Player metadata
  • Audio guidance
  • Video/audio exports where rendered

Always verify current locale support in the API docs.

Docs:

Content Sources

Hyperhuman can power workouts from different sources.

Source Best For
premium_stock Production-quality workouts and consistent visuals
team_exercises Fully branded content from your own library
free_stock Testing, prototyping, low-risk evaluation

For production, use:

  • premium_stock for quality and consistency
  • team_exercises for full brand alignment
  • Collection exclusions when you need tighter visual control

Example:

{
  "exerciseSources": ["premium_stock"],
  "excludeExerciseCollections": [
    "Free - Outdoor",
    "Premium - Industrial"
  ]
}

Docs:

Nutrition, AI Coach, and Member Intelligence

The API can also support deeper member experiences around nutrition, coaching, and insight loops.

Product Area What It Enables Docs
Nutrition logging Meal photo analysis, confirmation, and daily nutrition signals Nutrition
AI Coach Conversational coaching and action confirmation AI Chat
Daily Digest Daily guidance across health, training, recovery, movement, nutrition, and body AI Insights

Use these when your product needs more than workout delivery.

This is where the experience moves from content playback to daily guidance.

Social, Automation, and Growth Workflows

The same content engine can support acquisition and lifecycle marketing.

Workflow What It Does Docs
Social Drops Export ready-made social video bundles, covers, and copy Social Drops
Social Publish Manage scheduled publishing automations Social Publish
Content Autopilot Schedule content generation, cloning, or publishing workflows Content Autopilot

Use these when your team wants to turn workouts, programs, and exercises into campaign assets without rebuilding content manually.

Product Metrics to Track

The API is not just for delivery.

It helps your product learn.

Metric Why It Matters
First workout started Activation
First workout completed First value
Weekly sessions completed Habit formation
Recommendation click-to-start Personalization quality
Generated workout completion AI quality
Adapt acceptance Relevance over time
Program start rate Journey adoption
Program completion Long-term adherence
Feedback rating Content quality
Difficulty rating Programming fit
Daily Digest opens Insight engagement
Return after missed session Re-engagement
D30 / D60 retention Product value
Churn Subscription health

Technical Implementation Checklist

Area Recommendation
API key security Keep API keys server-side
Metadata Cache categories, equipment, muscle groups, feedback options
Pagination Use documented pagination patterns and follow links.next where available
IDs Treat all IDs as opaque strings
Errors Handle non-2xx responses through the standard error envelope
Rate limits Back off on 429; retry 500+ carefully
Heavy endpoints Budget for higher-cost calls on AI and export endpoints
Stream URLs Treat pre-signed URLs as temporary and refresh when needed
Generated content Store returned generated workout or plan data if you need to reference it later
Session tracking Patch progress during playback, not only at the end
Localization Pass locale consistently across details, playlists, and exports
Search Use metadata and filters before custom search logic
Observability Log endpoint latency, error codes, quota usage, and user-level conversion

Recommended Technical Architecture

For MVPs

Frontend
  → Backend proxy
    → Hyperhuman Content API
      → Embedded player / hosted library

Best for:

  • Corporate wellness portals
  • Web-based pilots
  • Landing page trials
  • Early-stage app validation

For mobile apps

Mobile app
  → Your backend
    → Hyperhuman Content API
      → Workout details
      → Playlist segments
      → HLS streams
      → Session tracking
      → Feedback
      → Recommend / Generate / Adapt

Best for:

  • Native iOS / Android apps
  • Premium consumer apps
  • Personalized fitness products
  • Connected health products

For connected hardware

Device UI / companion app
  → Your backend
    → Hyperhuman Content API
      → Machine-specific workouts
      → Structured playlist
      → Session tracking
      → User feedback
      → Adaptation

Best for:

  • Smart gym equipment
  • Resistance machines
  • Connected home fitness
  • Wearable-driven products

For enterprise wellness

Employer portal
  → Your backend
    → Hyperhuman Content API
      → Embedded library
      → Programs
      → End-user lifecycle
      → Usage and insights

Best for:

  • Corporate wellness
  • Benefits platforms
  • Employee wellbeing
  • B2B client workspaces

Where the API Fits in Your Stack

Product Layer Build Yourself Use Hyperhuman
User accounts Yes Optional support through end-user lifecycle
Entitlements Yes Can map to org/user access
Content library Optional Yes
Exercise metadata No Yes
Workout playback Optional Embed, stream, or custom player
Full video exports No Yes
Audio workout exports No Yes
AI workout logic No Yes
Recommendations No Yes
Adaptive sessions No Yes
Daily insights No Yes
Session tracking Integrate Yes
Analytics and usage Integrate Yes
Social assets Optional Yes
Automations Optional Yes

When to Use API vs Branded App

Need Best Path
We already have an app Content API
We need full UX control Content API + custom player
We need to launch fast without building app UX White-label branded app
We need a web pilot Embed & Go
We need content inside a portal Embed or API
We need advanced personalization in our own product Content API
We need standard member app with subscriptions Branded app
We need both app and API infrastructure Platform / Ultra path

Explore:

What Makes This Different

Most fitness APIs give you content.

Hyperhuman gives you the operating layer around content.

Typical Content API Hyperhuman Content API
Static videos Structured workouts and programs
Basic metadata Rich workout, exercise, equipment, difficulty, playlist, and media data
No personalization Recommend, Generate, Adapt
No feedback loop Sessions, feedback, insights
No native content ops Teams workspace and Smart Library
No delivery flexibility Embeds, streams, audio, full video, custom player
No AI-ready docs OpenAPI, LLM bundle, agent guide
No growth surface Social Drops and automation
No branded app path API plus white-label app option

Adoption Roadmap

Start simple.

Then add intelligence.

Stage What to Ship Outcome
Stage 1 Browse + play workouts Real content in product
Stage 2 Metadata + filters Better discovery
Stage 3 Recommendations Personalized “Next Up”
Stage 4 Session tracking + feedback Learn what works
Stage 5 Generate workouts / plans Dynamic personalization
Stage 6 Adapt workouts / plans Evolving journeys
Stage 7 Daily Digest + pillar insights Retention loops
Stage 8 Social Drops + automation Growth and content ops
Stage 9 Branded app or deeper modules Full member experience

Management View: Why Adopt the API

For engineering leaders, the API reduces build scope.

For product leaders, it accelerates personalization.

For business leaders, it shortens time-to-market.

Business Goal API Impact
Faster launch Ship content and playback in days
Lower build risk Avoid building video, metadata, AI, and content ops from scratch
Better retention Add recommendations, adaptation, feedback, and insights
Better personalization Use goals, level, equipment, duration, behavior, and context
Lower content ops Reuse Smart Library, stock, licensed, and team-owned content
More delivery options App, web, embeds, API, audio, video, custom player
Global reach Localized metadata and media where supported
Future flexibility Start with embeds, grow into full custom UX

Developer Resources

Use the API overview for the product picture.

Use the docs for implementation.

Use the OpenAPI files for codegen, SDKs, and technical review.

Need Best Link
Product overview Hyperhuman Content API Overview
API introduction Docs Introduction
Full API docs API Docs
OpenAPI JSON OpenAPI JSON
OpenAPI YAML OpenAPI YAML
LLM implementation bundle LLM Bundle
Agent implementation guide Agent Guide
Custom player guide Custom Player Guide

API Docs by Theme

Theme What to Use It For Docs
Workouts, playlists, streams Browse workouts, fetch details, build players, stream video/audio Workouts
Plans and programs Build multi-week training journeys Plans
AI recommendations Recommend the best next workout or plan from existing content AI Recommendation
AI generation Generate new workouts and programs from goals, level, equipment, and duration AI Generation
AI adaptation Adapt existing workouts and plans as users progress AI Adaptation
User management Invite, find, suspend, reactivate, and remove end users End-user Management
End-user plans Start plans, track active plan progress, and manage auto-adapt End-user Plans
AI insights Power Daily Digest, readiness signals, and pillar views AI Insights
Nutrition photo logging Add AI meal photo analysis and confirmation flows Nutrition
AI coach chat Add AI coach conversations and action confirmation AI Chat
Organization settings Fetch branding, join options, metadata, and usage stats Organization
Exercise library Browse workspace exercise assets for builders and catalogs Library Exercises
Exercise groups Use circuits, sets, and micro-workouts Exercise Groups
Content automation Schedule content generation, cloning, or publishing workflows Content Autopilot
Social Drops Export ready-made social video bundles, covers, and copy Social Drops
Social publishing Manage scheduled publishing automations Social Publish

Production Readiness Checklist

Before launch, confirm:

Area Ready When
Credentials API key and organization ID are stored securely
Backend proxy API calls are routed through your backend
Metadata cache Categories, equipment, muscle groups, and feedback options are cached
Content access Workouts and plans are filtered to your product scope
Playback Embedded player, full stream, or custom playlist renderer is tested
Sessions Start, progress, end, complete, and feedback flows work
Personalization Recommend, Generate, and/or Adapt flows are validated
Localization Locale strategy is defined and tested
Error handling 400, 401, 403, 404, 429, and 500+ paths are handled
Rate limits Heavy endpoints are budgeted and monitored
Analytics Product events are mapped to business KPIs
Support Debug logs include request IDs, endpoint, status, latency, and user reference

Final Takeaway

Building a personalized fitness experience should not require building a content studio, video pipeline, workout engine, recommendation layer, adaptive programming model, insights system, and app delivery stack from scratch.

Hyperhuman gives technical teams the infrastructure.

You build the product.

Start with content.
Add personalization.
Track behavior.
Adapt over time.
Turn insight into retention.

That is the path from API integration to intelligent fitness experience.

Explore the Hyperhuman Content API, read the API docs, or get started in Hyperhuman Teams.

Build faster.
Personalize deeper.
Ship smarter.