Skool Doesn't Publish a Changelog. Its Creators Are Writing One in the Comments.

There is a post sitting inside Educate with Skool right now titled "✳️ September 2026 Skool Feature Updates." It has 18 comments. The most recent one landed three days ago. The setup is simple: click the bell icon to follow the thread, and the author will post all the September updates they find out about in the comment section.

Read that again. Find out about.

This is not a Skool employee publishing release notes. It's a community member keeping a running log of what changed on a platform that charges them monthly, because nobody else is doing it. The same format ran in February and March, and again in June. It's become a monthly ritual.

No /changelog, no email, no list

Skool.com doesn't run a public changelog. Updates ship through a mix of in-product banners, Sam Ovens' personal Twitter and YouTube, occasional posts in the Skool Community, and creators noticing changes after the fact. There's no email-based changelog and no dedicated /changelog URL. Founders who want a stream of updates have to piece it together themselves.

Plenty shipped in that window. From late 2024 through 2026: a redesigned mobile app, a calendar feature that syncs to external calendars, classroom video improvements including chapter markers, a redesigned leaderboard with weekly and all-time tabs, anti-spam tightening on DMs from new accounts, and payment processing improvements for non-US cards. A sweeping Discovery overhaul — new search, new ranking algorithm, new categories, a trending homepage — was revealed in a video update from Skool's founders.

Good changes, mostly. Announced the way a friend tells you about a restaurant.

What you can't build on

The missing changelog is a symptom. The bigger gap is that you cannot programmatically see your own community.

As of 2026, Skool publishes no public API. No developer docs site, no API key dashboard, no rate-limit table. An independent API Evangelist profile calls this a deliberate, long-standing product decision favouring simplicity over an extensible integration surface. The only official integration is a Zapier plugin locked to the $99-per-month Pro plan. The Hobby tier gets no API key, no Zapier, no webhooks.

And the Zapier surface is thin. There's no trigger for a new post, comment, level-up, cancellation, or failed payment, and no action to remove a member or post on their behalf. You can't pull analytics into your own dashboard. Granular role permissions are still absent too.

The workaround economy tells you how badly people want in. One Apify actor openly reverse-engineers Skool's internal endpoints and resells them as a clean API, working around cookies, an AWS WAF token and a build ID that rotates roughly weekly.

The trade nobody signed

There's a real argument for the closed door. A documented API is a gift to scammers running mass-DM blasts and fake-engagement bots, and Skool's reputation as a clean platform is part of the product.

But the silence isn't free. If your revenue lives inside someone else's product, the roadmap is part of what you're buying. On Skool, the roadmap is 18 comments deep in a thread a member started for free.