canonical: https://jentic.com/apis/wger.de/wger

# Wger De wger

Self hosted FLOSS workout and fitness tracker. The API exposes 256 endpoints secured with apiKey, bearer authentication.

## For AI agents

Programmatically check_permission_retrieve, day_create. Covers 256 operations with apiKey, bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- check_permission_retrieve
- day_create
- day_list
- day_retrieve
- day_update
- day_partial_update
- day_destroy

## Use cases

### Developer Tools Operations

Use the wger to perform developer tools operations programmatically. The API provides 256 endpoints covering core functionality including check_permission_retrieve, day_create, day_list.

Example prompt: Call GET `/api/v2/check-permission`/ to check_permission_retrieve

### Automated Check Permission Management

Automate check permission operations by combining multiple wger endpoints. Agents can day_create and then day_list in a single workflow.

Example prompt: Call POST `/api/v2/day`/ to day_create, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call wger endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, bearer tokens manually.

Example prompt: Search Jentic for 'check_permission_retrieve', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/v2/check-permission/` | check_permission_retrieve |
| POST | `/api/v2/day/` | day_create |
| GET | `/api/v2/day/` | day_list |
| GET | `/api/v2/day/{id}/` | day_retrieve |
| PUT | `/api/v2/day/{id}/` | day_update |
| PATCH | `/api/v2/day/{id}/` | day_partial_update |
| DELETE | `/api/v2/day/{id}/` | day_destroy |
| GET | `/api/v2/deletion-log/` | deletion_log_list |

## Key resources

- **Check Permission** — Operations for check permission
- **Day** — Operations for day
- **Deletion Log** — Operations for deletion log
- **Equipment** — Operations for equipment
- **Exercise** — Operations for exercise

## Why Jentic

- **Setup:** Wiring the wger API by hand means picking between its token header auth and JWT bearer auth and handling retries yourself across its large v2 surface. Through Jentic you install once, import wger from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** wger puts the resource id in the URL path (`/api/v2/day/{id}`/), so a rule can pin your agent to reading a training day and nothing else. You choose the operations it may call, so destructive ones like deleting or overwriting a day with PUT or DELETE are not included unless you add them.
- **Credential handling:** Your wger token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check a permission' or 'read a training day', and Jentic returns the matching wger operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the wger use?

The wger uses apiKey, bearer authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I check_permission_retrieve with the wger?

Yes. Use the GET `/api/v2/check-permission`/ endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the wger?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I check_permission_retrieve through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check_permission_retrieve'. Jentic returns the matching wger operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the wger have?

The wger exposes 256 endpoints covering check permission, day, deletion log operations.

### Can I limit what my agent is allowed to do with the wger API?

Yes. Because you run Jentic One yourself, your own rules decide which wger operations and credentials the agent may use. wger puts the resource id in the URL path, such as `/api/v2/day/{id}`/, so a rule can pin the agent to reading a single training day and nothing else. You pick the operations it may call, so destructive ones like overwriting a day with PUT or deleting it with DELETE stay off limits unless you add them.