canonical: https://jentic.com/apis/staging.api.ekklo.com/staging-api-ekklo

# Staging Api Ekklo Ekklo API

Ekklo is a coaching platform that helps fitness coaches manage their clients, send invitations, and automate client workflows. The API exposes 26 endpoints secured with bearer authentication.

## For AI agents

Programmatically create an activity, list activities. Covers 26 operations with bearer authentication.

## Scope

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

## Capabilities

- Create an activity
- List activities
- Sync activities
- Update an activity
- Delete an activity
- Send AI chat message

## Use cases

### Developer Tools Operations

Use the Ekklo API to perform developer tools operations programmatically. The API provides 26 endpoints covering core functionality including create an activity, list activities, sync activities.

Example prompt: Call POST `/api/v1/activities` to create an activity

### Automated Activities Management

Automate activities operations by combining multiple Ekklo API endpoints. Agents can list activities and then sync activities in a single workflow.

Example prompt: Call GET `/api/v1/activities` to list activities, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Ekklo 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 bearer tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/v1/activities` | Create an activity |
| GET | `/api/v1/activities` | List activities |
| POST | `/api/v1/activities/sync` | Sync activities |
| PUT | `/api/v1/activities/{uuid}` | Update an activity |
| DELETE | `/api/v1/activities/{uuid}` | Delete an activity |
| POST | `/api/v1/ai/chat` | Send AI chat message |
| GET | `/api/v1/ai/conversations` | List AI conversations |
| GET | `/api/v1/ai/conversations/{id}` | Get a conversation |

## Key resources

- **Activities** — Activity management
- **AI** — AI chat and conversations
- **Integrations** — Third-party integrations
- **Auth** — Authentication
- **Programs** — Programs and repetitions

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 63 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 83 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 53 / 100
- **View full report:** https://jentic.com/apis/staging.api.ekklo.com/staging-api-ekklo/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Ekklo API by hand means learning its bearer auth against staging.api.ekklo.com and managing activity and AI conversation calls yourself. Through Jentic you install once, import the Ekklo API from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** Ekklo puts the activity id in the URL path (`/api/v1/activities/{uuid}`), so a rule can pin your agent to reading and creating activities. You choose the operations it may call, so ones like deleting an activity are not included unless you add them.
- **Credential handling:** Your Ekklo bearer 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 'create an activity' or 'list AI conversations', and Jentic returns the matching Ekklo API 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 Ekklo API use?

The Ekklo API uses a Bearer token 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 an activity with the Ekklo API?

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

### What are the rate limits for the Ekklo 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 an activity through Jentic?

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

### How many endpoints does the Ekklo API have?

The Ekklo API exposes 26 endpoints covering activities, ai, integrations operations.

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

Yes. Because you self-host Jentic One, you decide which Ekklo API operations your agent may call, so you can pin it to read-only actions like listing activities (GET `/api/v1/activities`) and creating activities (POST `/api/v1/activities`) while excluding others. Since the activity id sits in the URL path (`/api/v1/activities/{uuid}`), destructive operations such as deleting an activity are left out unless you explicitly add them to your rules. Your own rules also govern which stored credentials the agent can use, so it only ever acts within the scope you set.