How I Reverse Engineered the Skool API (And Ended Up Publishing a Chrome Extension)

Skool doesn't have a public API. Full stop. And when you need to automate something on a platform that doesn't have one, you have three options: use Selenium to simulate clicks like it's 2015, accept that it can't be done, or get creative. I chose the third. The Real Problem I have a community on Skool — Cágala, Aprende, Repite . I wanted to automate certain tasks: detect new posts without replies, respond from Telegram, publish without me having to be in front of the screen. The problem: Skool doesn't offer an official API. Everything their app does passes through internal calls they never documented. The obvious solution for a developer: see what happens in Chrome's DevTools when you use Skool as a normal user. Every click, every scroll, every action fires HTTP requests. Those requests have endpoints, headers, payloads. That's the API you need — it just was never written in Swagger. The problem with DevTools: it's manual, uncomfortable, and you have to copy each request by hand. For