Wger
wger (wger Workout Manager) is a self-hosted, free and open source (AGPL-3.0) fitness, workout, nutrition and body-weight tracker written in Django. Its REST API is served under /api/v2/ on any wger instance — including the project's own hosted instance at wger.de — and publishes a complete OpenAPI 3.0.3 schema generated from the code at /api/v2/schema, covering 129 paths and 254 operations across routines, days, slots and per-iteration progression configs, workout logs and sessions, the community exercise database (exercises, translations, images, videos, muscles, equipment, categories), the ingredient and nutrition-plan catalog with an incremental ingredient-sync feed, body weight, body measurements, galleries and gamification trophies. System-wide reference data (exercises, ingredients, units) is readable without authentication; user-owned data takes a personal API token, a JWT issued via allauth-headless, an OAuth2/OIDC access token, or the session cookie. The project also ships a first-party Python API client, a first-party MCP server exposing 85 tools over the same API, React components, Flutter and Android apps, and Docker/Helm deployment stacks.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Wger the way a machine reads it — 70 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Wger scores 46.2/100 (developing), with a separate agent-readiness read of 34/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from Wger's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/wger/"
title="Wger on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/wger.svg"
alt="Wger Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/wger/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/wger/"
title="Wger on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/wger/card.svg"
alt="Wger Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Wger
Each block below is one kind of artifact we hold for Wger. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 63
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Wger Check Language API
The check-language API from Wger — 1 operation(s) for check-language.
Wger Check Permission API
The check-permission API from Wger — 1 operation(s) for check-permission.
Wger Day API
The day API from Wger — 2 operation(s) for day.
Wger Deletion Log API
The deletion-log API from Wger — 2 operation(s) for deletion-log.
Wger Equipment API
The equipment API from Wger — 2 operation(s) for equipment.
Wger Exercise API
The exercise database. Related objects are referenced by ID. This is the writable endpoint of the two exercise representations.
Wger Exercise Submission API
The exercise-submission API from Wger — 1 operation(s) for exercise-submission.
Wger Exercise Translation API
The exercise-translation API from Wger — 2 operation(s) for exercise-translation.
Wger Exercisealias API
The exercisealias API from Wger — 2 operation(s) for exercisealias.
Wger Exercisecategory API
The exercisecategory API from Wger — 2 operation(s) for exercisecategory.
Wger Exercisecomment API
The exercisecomment API from Wger — 2 operation(s) for exercisecomment.
Wger Exerciseimage API
The exerciseimage API from Wger — 3 operation(s) for exerciseimage.
Wger Exerciseinfo API
The same exercises read-only, with categories, muscles, equipment, images, videos and translations expanded inline. Meant for external tools and integrations: one request return...
Wger Gallery API
The gallery API from Wger — 2 operation(s) for gallery.
Wger Ingredient API
Nutritional information per ingredient, referencing related objects by ID. Read-only and rate limited.
Wger Ingredient Image API
The ingredient-image API from Wger — 2 operation(s) for ingredient-image.
Wger Ingredient Sync API
The same data as ingredientinfo, but cursor paginated for mirroring the whole catalogue. No `count`, and only `next`/`previous` rather than arbitrary offsets. Combine with the `...
Wger Ingredientinfo API
The same ingredients read-only, with language, license, image and weight units expanded inline. Meant for external tools and integrations: one request returns everything, with n...
Wger Ingredientweightunit API
The ingredientweightunit API from Wger — 2 operation(s) for ingredientweightunit.
Wger Issue Refresh Token API
The issue-refresh-token API from Wger — 1 operation(s) for issue-refresh-token.
Wger Language API
The language API from Wger — 2 operation(s) for language.
Wger License API
The license API from Wger — 2 operation(s) for license.
Wger Max Repetitions Config API
Upper limit for the repetitions of a set, per iteration.
Wger Max Rest Config API
Upper limit for the rest between sets, per iteration.
Wger Max Rir Config API
Upper limit for the reps in reserve of a set, per iteration.
Wger Max Sets Config API
Upper limit for the number of sets, per iteration.
Wger Max Weight Config API
Upper limit for the weight of a set, per iteration.
Wger Meal API
The meal API from Wger — 3 operation(s) for meal.
Wger Mealitem API
The mealitem API from Wger — 3 operation(s) for mealitem.
Wger Measurement API
The measurement API from Wger — 2 operation(s) for measurement.
Wger Measurement Category API
The measurement-category API from Wger — 2 operation(s) for measurement-category.
Wger Min App Version API
The min-app-version API from Wger — 1 operation(s) for min-app-version.
Wger Min Server Version API
The min-server-version API from Wger — 1 operation(s) for min-server-version.
Wger Muscle API
The muscle API from Wger — 2 operation(s) for muscle.
Wger Nutritiondiary API
The nutritiondiary API from Wger — 3 operation(s) for nutritiondiary.
Wger Nutritionplan API
Nutrition plans, referencing meals and items by ID.
Wger Nutritionplaninfo API
The same plans read-only, with meals, items and their nutritional values expanded inline. Meant for external tools and integrations that want a whole plan in one request, with n...
Wger Powersync Keys API
The powersync-keys API from Wger — 1 operation(s) for powersync-keys.
Wger Powersync Token API
The powersync-token API from Wger — 1 operation(s) for powersync-token.
Wger Public Templates API
Read-only view of the routine templates published by other users.
Wger Repetitions Config API
Repetitions for a set, per iteration.
Wger Rest Config API
Rest between sets, per iteration.
Wger Rir Config API
Reps in reserve for a set, per iteration.
Wger Routine API
Workout routines. The nested day, slot and config structure is available in one request under `/routine/{id}/structure/`.
Wger Schema API
The schema API from Wger — 1 operation(s) for schema.
Wger Sets Config API
Number of sets, per iteration.
Wger Setting Repetitionunit API
The setting-repetitionunit API from Wger — 2 operation(s) for setting-repetitionunit.
Wger Setting Weightunit API
The setting-weightunit API from Wger — 2 operation(s) for setting-weightunit.
Wger Slot API
The slot API from Wger — 2 operation(s) for slot.
Wger Slot Entry API
The slot-entry API from Wger — 2 operation(s) for slot-entry.
Wger Templates API
Read-only view of the routines the user marked as a template, plus their trainer's, if they have one.
Wger Token API
The token API from Wger — 2 operation(s) for token.
Wger Trophy API
The trophy API from Wger — 3 operation(s) for trophy.
Wger Upload Powersync Data API
The upload-powersync-data API from Wger — 1 operation(s) for upload-powersync-data.
Wger User Statistics API
The user-statistics API from Wger — 2 operation(s) for user-statistics.
Wger User Trophy API
The user-trophy API from Wger — 2 operation(s) for user-trophy.
Wger Userprofile API
The userprofile API from Wger — 2 operation(s) for userprofile.
Wger Version API
The version API from Wger — 1 operation(s) for version.
Wger Video API
The video API from Wger — 2 operation(s) for video.
Wger Weight Config API
Weight for a set, per iteration.
Wger Weightentry API
The weightentry API from Wger — 2 operation(s) for weightentry.
Wger Workoutlog API
The workoutlog API from Wger — 2 operation(s) for workoutlog.
Wger Workoutsession API
The workoutsession API from Wger — 2 operation(s) for workoutsession.
Scroll within the panel for all 63 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
wger MCP server
First-party MCP server, maintained in the wger-project GitHub organization, that exposes the wger (>= 2.6) fitness/nutrition REST API as MCP tools — routines, workout logging, s...
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Wger Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Wger Rate Limits
RATE LIMITSSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Wger — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/wger · machine-readable index on apis.io
This is an independent, third-party profile of Wger, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.