canonical: https://jentic.com/apis/teambuildr.com/teambuildr

# TeamBuildr Strength API

TeamBuildr is a strength and conditioning platform. The API provides access to athletes, workouts, exercises, and performance tracking. The API exposes 14 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create athlete, list athletes. Covers 14 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create Athlete
- List Athletes
- Get Athlete
- Update Athlete
- Delete Athlete

## Use cases

### Analytics Operations

Use the TeamBuildr Strength API to perform analytics operations programmatically. The API provides 14 endpoints covering core functionality including create athlete, list athletes, get athlete.

Example prompt: Call POST /athletes to create athlete

### Automated Athletes Management

Automate athletes operations by combining multiple TeamBuildr Strength API endpoints. Agents can list athletes and then get athlete in a single workflow.

Example prompt: Call GET /athletes to list athletes, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TeamBuildr Strength API 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 tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/athletes` | Create Athlete |
| GET | `/athletes` | List Athletes |
| GET | `/athletes/{athlete_id}` | Get Athlete |
| PUT | `/athletes/{athlete_id}` | Update Athlete |
| DELETE | `/athletes/{athlete_id}` | Delete Athlete |
| POST | `/workouts` | Create Workout |
| GET | `/workouts` | List Workouts |
| GET | `/workouts/{workout_id}` | Get Workout |

## Key resources

- **Athletes** — Athlete management
- **Workouts** — Workout management
- **Exercises** — Exercise catalog
- **Performance** — Performance tracking
- **Teams** — Team management

## Why Jentic

- **Setup:** Wiring the TeamBuildr Strength API by hand means registering its API key, threading that header onto every call against api.teambuildr.com/v1, and writing the paging and retry glue for athlete and workout records yourself. Through Jentic you install once, import the TeamBuildr Strength API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The TeamBuildr Strength API puts the athlete id in the URL path (`/athletes/{athlete_id}`), so a rule can pin your agent to one athlete: it can read and update that athlete's records and nothing else. You choose the operations it may call, so destructive ones like deleting an athlete are not included unless you add them.
- **Credential handling:** Your TeamBuildr API key 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 'create an athlete' or 'log a workout', and Jentic returns the matching TeamBuildr Strength API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the TeamBuildr Strength API use?

The TeamBuildr Strength API uses an API key passed in the `Authorization` header. 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 create athlete with the TeamBuildr Strength API?

Yes. Use the POST /athletes endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the TeamBuildr Strength API?

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 create athlete through Jentic?

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

### How many endpoints does the TeamBuildr Strength API have?

The TeamBuildr Strength API exposes 14 endpoints covering athletes, workouts, exercises operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which TeamBuildr Strength API operations and credentials your agent may use. Since the athlete id sits in the URL path (`/athletes/{athlete_id}`), a rule can pin the agent to a single athlete so it only reads and updates that athlete's records and nothing else. You also choose which operations are allowed, so destructive calls like DELETE `/athletes/{athlete_id}` stay off the list unless you add them.