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

# Skool API (SkoolAPI)

SkoolAPI is a third-party REST API providing programmatic access to Skool community platform functionality. It covers members, posts, groups, community chat, analytics, and webhooks. The API is in early stages with limited endpoint coverage. All endpoints require API key authentication and an active session. Note: Skool does not publish an official first-party public API; this spec covers the Skoo. The API exposes 16 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create a session, list groups. Covers 16 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Create a session
- List groups
- Get a group
- Query and filter Skool API (SkoolAPI) records by parameters
- Monitor Skool API (SkoolAPI) operational status and events

## Use cases

### Identity and Authentication Operations

Use the Skool API (SkoolAPI) to perform identity auth operations programmatically. The API provides 16 endpoints covering core functionality including create a session, list groups, get a group.

Example prompt: Call POST `/v1/sessions`/ to create a session

### Automated Groups Management

Automate groups operations by combining multiple Skool API (SkoolAPI) endpoints. Agents can list groups and then get a group in a single workflow.

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

### AI Agent Integration via Jentic

AI agents discover and call Skool API (SkoolAPI) 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 a session', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/sessions/` | Create a session |
| GET | `/v1/groups/` | List groups |
| GET | `/v1/groups/{group_slug}/` | Get a group |
| GET | `/v1/groups/{group_slug}/members/` | List group members |
| GET | `/v1/groups/{group_slug}/members/{member_id}/` | Get a member |
| POST | `/v1/groups/{group_slug}/posts/` | Create a post |
| GET | `/v1/groups/{group_slug}/posts/` | List group posts |
| GET | `/v1/groups/{group_slug}/posts/{post_id}/` | Get a post |

## Key resources

- **Groups** — Operations for groups
- **Sessions** — Operations for sessions
- **Webhooks** — Operations for webhooks

## 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:** 62 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 61 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/skool.com/skool/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 Skool API by hand means creating a session, then sending your key in the secret-key header to api.skoolapi.com on every request to the groups, members, and posts endpoints. Through Jentic you install once, import Skool from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Skool puts the group slug in the URL path (`/v1/groups/{group_slug}/members` and /posts), so a rule can pin your agent to one group. You choose the operations it may call, so if you only grant reading members and posts, creating posts is not included unless you add it.
- **Credential handling:** Your Skool 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 'list members of a group' or 'create a post in a group', and Jentic returns the matching Skool operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Skool API (SkoolAPI) use?

The Skool API (SkoolAPI) uses an API key passed in the `X-Api-Secret` 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 a session with the Skool API (SkoolAPI)?

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

### What are the rate limits for the Skool API (SkoolAPI)?

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 a session through Jentic?

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

### How many endpoints does the Skool API (SkoolAPI) have?

The Skool API (SkoolAPI) exposes 16 endpoints covering groups, sessions, webhooks operations.

### Can I limit what my agent is allowed to do with the Skool API (SkoolAPI)?

Yes. Because Jentic One is self-hosted, you set the rules that decide which Skool operations and credentials your agent may use. The group slug lives in the URL path (`/v1/groups/{group_slug}/members` and /posts), so a rule can pin the agent to a single community. You also choose the operations it may call, so granting only reading members and posts leaves creating posts out unless you add that endpoint yourself.