Your first request

Every TryHelper action runs through a single endpoint. Send an action, the groupSlug, and any params. Authenticate with a bearer key from your dashboard.

# Run any action against a connected group
curl -X POST https://tryhelper.co/v1/execute \
  -H "Authorization: Bearer sk_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "posts:create",
    "groupSlug": "your-community",
    "params": { "title": "Weekly Update", "content": "Great work!" }
  }'

const res = await fetch("https://tryhelper.co/v1/execute", {
  method: "POST",
  headers: {
    Authorization: "Bearer " + process.env.TRYHELPER_KEY,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    action: "posts:create",
    groupSlug: "your-community",
    params: { title: "Weekly Update" },
  }),
});
const data = await res.json();

import requests

res = requests.post(
    "https://tryhelper.co/v1/execute",
    headers={"Authorization": f"Bearer {TRYHELPER_KEY}"},
    json={
        "action": "posts:create",
        "groupSlug": "your-community",
        "params": {"title": "Weekly Update"},
    },
)
print(res.json())

Base URL · https://tryhelper.co

Two layers of auth

TryHelper separates your account auth from Skool's session. You authenticate to TryHelper with a bearer key or OAuth; TryHelper holds the Skool session for each connected group and refreshes it for you.

One login, reused for days

Connecting logs into Skool once and stores the session cookies (encrypted). Each call carries a groupSlug, so one admin login can operate every community you manage.

Tool reference

35 actions, plus skool_list_groups to list the communities connected to your account. The REST action and the MCP tool name (skool_*) are two faces of the same call.

REST endpoints

Never a hard fail

Actions return 200 with a JSON body — check success first. On failure you get an error message and an errorCode you can branch on.

Stay under the ceiling

Limits apply per account + group, with stricter ceilings on heavy actions (bans, removals, exports). Both the MCP and REST paths share the same limiter.

Exceed a window and you'll get RATE_LIMIT — back off 60–120 seconds and retry. For bulk jobs, queue writes and spread them across minutes.