Food and fitness · wger

fitness.exercises

Searches a bounded, cached index of publicly licensed English exercise instructions. Each result retains its source, author and licence. Exercise information is not a diagnosis or a personalized injury-safe training prescription.

Operation: POST /v1/capabilities/fitness.exercises/execute
operationId: executeFitnessExercises
Typical credits: 0
Search deadline: 15 s server-side
Paging: local
Availability: ConfiguredChecked 2026-09-23 21:02 UTC

Cost basis: Public exercise data; zero per-call provider charge. Availability is reported per deployment by GET /v1/catalog (available). The timestamped snapshot describes configuration, not provider uptime or your account's enabled choices. Check the catalog with your own key before a call. Credits are explained under credits and limits.

Request

Body of POST /v1/capabilities/fitness.exercises/execute, JSON, validated against the FitnessExercisesRequest component of the public OpenAPI document. Defaults are applied server-side, so an omitted optional field behaves exactly as its default.

Request fields of fitness.exercises
Field	Type	Required	Default	Constraints and description
query	string	no		min length 1, max length 120
equipment	string	no		min length 1, max length 120
muscle	string	no		min length 1, max length 120
num	integer	no	10	min 1, max 20

Search licensed English exercise descriptions by words, equipment and muscle. General exercise information, not injury-specific advice.
Unknown keys are rejected with 400 invalid_request.

Rules the schema cannot express

Checked after schema validation; violations return 400 invalid_request with a plain message.

Filters must not be blank.

Examples

Exercises

curl

curl -s -X POST https://api.powerups-ai.store/v1/capabilities/fitness.exercises/execute \
  -H "Authorization: Bearer $AIPA_API_KEY" -H "Content-Type: application/json" \
  -d '{"query":"squat","num":5}'

No recorded response is published for this capability yet. The envelope is the ExecuteResponse component (see sessions and records); the record keys below are what the adapter emits. A first call with the example above returns search_id, the records and the charge.

Result record

Every item in results[] carries record_id and title (contract, always present) and usually url and snippet. The keys below are the documented tier: produced deterministically by this capability, omitted when the source has no value, checked against recorded source fixtures in our test suite, and published as the FitnessExercisesRecord component (all optional, extra keys allowed) so generated clients type them. The wire schema itself still validates only the base keys. See stability tiers.

Record keys of fitness.exercises
Key	Type	Presence
equipment	string[]	when the source has it
muscles	string[]	when the source has it
secondary_muscles	string[]	when the source has it
attribution	string	always
author	string	when the source has it
licence	object	always

Caveats

Details are served from the record stored at search time without a provider call. When that stored detail is no longer available the call returns 410 session_expired ("the cached record detail is no longer available. Run the search again."); it is never re-fetched.

Follow-ups

Paging: Whole result set held in the session; more is served locally and costs nothing. Send { "search_id": "…", "action": "more" } while has_more is true; tolerate an empty page and stop after a bounded number of pages.
Update: Re-run with changed parameters (merged into the stored query); page state resets, search_id stays. Params accept any subset of the request fields (FitnessExercisesUpdateParams).
Record actions:
- details: Cached licensed exercise instructions, equipment, muscles and attribution.
Detail behaviour: Stored at search time; details is free and never calls the provider. details returns the stored exercise at no charge.

record action

curl -s -X POST https://api.powerups-ai.store/v1/follow-up \
  -H "Authorization: Bearer $AIPA_API_KEY" -H "Content-Type: application/json" \
  -d '{"record_id":"rec_…","action":"details"}'

Record detail objects of this capability are provider-shaped: documented by observation, not by schema. Full follow-up semantics: follow-up.

Typed client

With types generated from the public document (see types, client and samples) the call is path-keyed and the body is checked at compile time:

TypeScript (openapi-fetch)

const { data, error } = await client.POST("/v1/capabilities/fitness.exercises/execute", {
  body: {
    "query": "squat",
    "num": 5
  },
});
if (error) throw new Error(`${error.error.code}: ${error.error.message}`);
for (const record of data.results) console.log(record.record_id, record.title);