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

# Mighty Networks Admin API

Jentic publishes the only available OpenAPI specification for Mighty Networks Admin API, keeping it validated and agent-ready. The Mighty Networks Admin API gives community operators programmatic control over a Mighty Networks community: members, spaces, posts, events, plans, subscriptions, and courseworks. It uses bearer-token authentication scoped to a network and exposes 104 endpoints under /admin/v1/networks/{network_id}/, covering the full creator-platform lifecycle from member onboarding through paid subscription management.

## For AI agents

Manage members, spaces, posts, events, plans, subscriptions, and courses inside a Mighty Networks community via the Admin API.

## Scope

Does not handle payment processing, end-user authentication, or content moderation outside Mighty Networks itself - use for managing the community's members, spaces, posts, events, plans, subscriptions, and courseworks only.

## Capabilities

- Create and update members in a Mighty Networks community, including profile fields and permissions
- Publish and edit posts inside specific spaces to drive community engagement
- Schedule events and manage RSVPs across a network's calendar
- Define paid plans and grant or revoke member subscriptions tied to those plans
- Curate courseworks (course content) and manage learner enrolment
- Retrieve network-level analytics on members, spaces, and content for reporting agents
- Remove inactive members or revoke subscriptions to enforce community policy

## Use cases

### Automated Member Onboarding

When a new sign-up arrives from a marketing form or paid funnel, an agent creates the member in Mighty Networks, subscribes them to the appropriate plan, and adds them to onboarding spaces. The user lands inside the community already enrolled, removing manual provisioning work for the operator.

Example prompt: Create a member with email and name via POST /admin/v1/networks/{network_id}/members, then subscribe them to plan id 'premium-2026'.

### Event-Driven Community Engagement

An agent listens to upcoming product launches or webinar schedules and creates corresponding Mighty Networks events in the right spaces. Posts are also published to announce the event and drive RSVPs from existing members.

Example prompt: Create an event in the 'Live Workshops' space for next Friday at 18:00 UTC and publish a post announcing it with a link to RSVP.

### Subscription Lifecycle Management

Tie payment events from a billing system into Mighty Networks plans by creating, upgrading, or revoking subscriptions through the Admin API. This keeps paid-access content correctly gated without operator intervention.

Example prompt: Revoke a member's subscription on plan id 'monthly' after a Stripe cancellation webhook fires for that member.

### Course Operations

Operators running cohort-based courses use an agent to enrol members in courseworks, post weekly content into a course space, and pull progress data for follow-up coaching.

Example prompt: Enrol 25 members into the 'Cohort 7 - AI Foundations' coursework and create a kickoff post in its space.

### Agent-Driven Community Operations via Jentic

Through Jentic, operators wire Mighty Networks operations into AI agents using semantic search rather than manual SDK plumbing. The bearer token is held in the vault and injected per request, so agents can manage members and content without ever holding a secret.

Example prompt: Use Jentic search 'create a member in mighty networks', load the schema for POST /admin/v1/networks/{network_id}/members, and execute with email, first name, and last name.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /admin/v1/networks/{network_id}/ | Get network details |
| GET | /admin/v1/networks/{network_id}/members | List members of a network |
| POST | /admin/v1/networks/{network_id}/members | Create a member |
| PATCH | /admin/v1/networks/{network_id}/members/{id}/ | Update a member |
| DELETE | /admin/v1/networks/{network_id}/members/{id}/ | Delete a member |
| GET | /admin/v1/networks/{network_id}/me | Get the authenticated user |

## Key resources

- **Members** — Create, list, update, and delete members of a network
- **Spaces** — Manage the discrete sub-communities (spaces) in a network
- **Posts** — Create and manage posts within spaces
- **Events** — Schedule and manage events and RSVPs
- **Plans** — Define paid plans for the community
- **Subscriptions** — Grant, update, or revoke member subscriptions to plans
- **Courseworks** — Create and manage course content and learner enrolment

## Why Jentic

- **Setup:** Wiring the Mighty Networks Admin API by hand means reading its bearer scheme, threading the network id through every member, space, and event path, and setting the Authorization header yourself. Through Jentic you install once, import the Mighty Networks Admin API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Mighty Networks puts the network and member in the URL path (/admin/v1/networks/{network_id}/members/{id}), so a rule can pin your agent to one network's members. You choose the operations it may call, so removing a member with a DELETE is not included unless you add it.
- **Credential handling:** Your Mighty Networks Admin API bearer token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a member in Mighty Networks' or 'list a network's spaces', and Jentic returns the matching Admin API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Circle API** — Direct competitor for paid community platforms with members, spaces, and events.
- **Discourse API** — Open-source forum platform offering an alternative community surface.
- **Teachable API** — Course-hosting platform that pairs with community memberships.

## FAQ

### Why is there no official OpenAPI spec for Mighty Networks Admin API?

Mighty Networks does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Mighty Networks Admin API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Mighty Networks Admin API use?

The API uses bearer token authentication. Operators generate an Admin API key from their network settings and pass it as Authorization: Bearer <token>. Through Jentic, this bearer token sits in the encrypted vault and is injected per request without entering the agent's context.

### Can I create paid subscriptions through this API?

Yes. The plans and subscriptions endpoints under /admin/v1/networks/{network_id}/ let you define paid plans and grant or revoke member subscriptions, which is how community operators tie external billing into Mighty Networks access control.

### What are the rate limits for the Mighty Networks Admin API?

Mighty Networks documents per-token rate limits in their Admin API guide; limits typically apply per network and respond with HTTP 429 when exceeded. Implement exponential backoff and respect the Retry-After header where present.

### How do I add a member to my community through Jentic?

Run pip install jentic, search for 'create a member in mighty networks', load the schema for POST /admin/v1/networks/{network_id}/members, and execute with the new member's email and name. Jentic injects your stored bearer token automatically.

### Does this API let me access another operator's network?

No. Bearer tokens are scoped to a single network and the network_id path parameter must match the token's network. Use a separate token issued by each operator to manage multiple networks.

### Can I limit what my agent is allowed to do with the Mighty Networks Admin API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. Since the network and member sit in the URL path (/admin/v1/networks/{network_id}/members/{id}), you can pin the agent to a single network's members and choose exactly which endpoints it may call, such as listing members with GET or creating them with POST. Destructive calls like DELETE on a member are excluded unless you add them, so the agent can only run the operations you have granted.