Components

API structure including core components and objects

The SkoolAPI is organized around three core components that work together to provide comprehensive access to Skool functionality. Understanding these building blocks will help you integrate more effectively.

Sessions

Sessions represent authenticated connections to individual Skool accounts and serve as the foundation for all API interactions. Think of a session as a secure bridge between your application and a specific Skool community - once established, you can perform actions on behalf of that account.

Every API request requires an active session to determine which Skool account and communities you're accessing. Sessions handle the authentication complexity so you can focus on building features.

Endpoints

Endpoints are the specific API routes that let you interact with different Skool resources like communities, posts, members, and Chats. Each endpoint corresponds to a particular action you can perform within Skool.

All endpoints require both API authentication and an active session to function.

Webhooks

Webhooks allow SkoolAPI to notify your application when specific events occur in your Skool communities. Instead of constantly polling our API for changes, webhooks push real-time updates directly to your application's endpoints.

Common webhook events include, post creations, comment additions, and chat messages. This enables you to build responsive applications that react immediately to community activity.