Complete Exercise Database
With Video Demonstrations

The free BASIC plan gives you 500 API calls a month through the interactive Playground on this site, so you can try the exercise, search, filtering, routine and workout endpoints against real responses before writing any code. No credit card is required and no card is stored. You can create an API key on this plan, but it is accepted only from the Playground and refused from your own application, so calling the API from your own code means moving to the TESTING plan ($10 per month) or higher.

BASIC is free and reaches the API only through the Playground on this site: 500 calls a month, and a key that the Playground accepts but your own application cannot use. TESTING costs $10 per month, includes 1,000 calls, and unlocks direct API access with your own key so your application can call the API itself. TESTING covers exercises, search, filtering and videos in English; routines, workouts, bodymap images and non-English languages need a higher plan.

Requests past your monthly quota return HTTP 429. The JSON body carries a message and an upgrade URL, plus the timestamp your quota resets when that is known, and a matching Retry-After header so a client can back off correctly instead of retrying in a loop. You are never charged for calls beyond your plan — there is no overage billing. Before you get there, usage-alert emails go out at 80%, 90% and 100% of your quota on the self-serve plans — custom plans get 80% and 100% — and your dashboard shows live usage against the limit. Upgrading raises the limit immediately.

Yes, all three, from your dashboard. Changing plan in either direction goes through a fresh checkout and takes effect as soon as that completes — a downgrade's smaller quota and narrower endpoint access apply immediately, not at your next renewal — and it applies to the API key you already have, so the key never changes and nothing needs redeploying. There is no automatic proration or credit: the new plan is charged in full at checkout while the old subscription runs out the period you already paid for, so switch close to your renewal date if the timing matters. Cancelling is scheduled rather than immediate: you keep your paid plan, its quota and its endpoints until the end of the period you have already paid for, you are not charged again, and the account then moves to the free plan. A monthly plan has no minimum term and no cancellation fee; an annual plan is a twelve-month commitment charged upfront, so cancelling it stops the renewal rather than refunding the year. Custom plans are the exception — those terms are whatever we agreed with you.

The API serves exercise, routine and workout text in 14 languages: English, Spanish, Portuguese, French, German, Italian, Polish, Russian, Turkish, Arabic, Persian, Hindi, Japanese and Chinese. Add a lang parameter — lang=pt-br, for example — to any data endpoint and you get translated names, instructions, muscles and categories back, while video and image URLs stay identical across languages. English is included on every plan; the other thirteen are available on the GROWTH plan and above, and to everyone in the free Playground.

We use API key authentication with the X-API-Key header. There is no OAuth flow — one header on one HTTPS request is the whole handshake for every data endpoint. The one exception is media: a native client can call POST /media/token to exchange a permanent key for a short-lived, media-only token, so the permanent key never ships inside an app binary. You can generate and manage keys from your dashboard, and each key can be revoked individually, so a leaked key can be cut off without disturbing your other integrations.

Yes. Your backend calls POST /media/token to exchange its permanent API key for a short-lived, media-only token, then hands your app a plain video URL with the token in the query string — so AVPlayer and ExoPlayer need no custom headers and your permanent key never reaches the device. Tokens expire after 15 minutes by default, work only on media endpoints (never on data endpoints), and stop working immediately if the key behind them is revoked. Treat the resulting URL as a credential for as long as it lives: anyone who obtains it can stream media against your quota until it expires, so keep it out of your own logs, analytics and crash reports, and do not put it in a shared cache — we redact it from ours. Media fetched with a token meters against your key's quota exactly as a keyed request does.

Yes. A transparent server-side proxy that holds your API key and passes our responses straight through to your app is permitted — useful if you'd rather not adopt media tokens. Two conditions: video is never written to disk or to a shared/CDN cache on your side, and you pass our response headers through unchanged (we send Cache-Control: no-store on video deliberately). What your edge may hold is exactly what the headers allow: exercise text and metadata for up to 30 days, and nothing else. Thumbnails are sent private, so they may be cached in the end user's own client for 24 hours but not at a shared edge; bodymap images are sent no-store and may not be cached at all; video is never stored anywhere on your side. Note that every /stream request counts as one API call, including each range request your player issues.

Data is served from a single dataset the API loads at startup, so when it changes, every plan sees the new data at the same moment — there is nothing to pull, no migration to run and no extra charge. The API is also unversioned: there is no /v1 prefix in any URL and no dated release to pin, so your integration keeps calling the same endpoints as the data grows. We publish notable changes in the changelog. We do not publish an update schedule, so if your planning depends on one, ask us rather than inferring it from this page.