Skip to main content
Membership.io is an API-first platform for membership businesses. It gives creators the building blocks for hubs, contacts, content, media, checkout, access control, community, email, and segmentation. The shortest way to understand the API:
  • A team owns the creator account and admin data.
  • A hub is the branded member destination.
  • A contact is a person in the creator’s world.
  • A hub membership says a contact belongs to a hub.
  • Products and checkout grant access.
  • Access rules decide what each member can see.
  • Content, pages, media, community, and email build the member experience around that access.

Quickstart

Make your first authenticated request and learn the request shape.

Modules

Every product area with its admin guide, API guides, and tags, in one order used everywhere.

Mental model

Understand teams, hubs, contacts, memberships, and access.

Authentication

Choose between platform JWTs, contact JWTs, and team API keys.

Using the admin

Create a hub and manage it from the Membership.io admin, with the matching API request for each step.

Connect an AI assistant

Give Claude, ChatGPT, or Cursor access to your team through the MCP server, with a sign-in and a consent screen.

MIO CLI

Install the command-line tool and build a hub end to end from a terminal or a coding agent.

API reference

Browse the generated OpenAPI reference and full endpoint inventory.

​
How these docs are organised

  • Start is this page, the quickstart, and the concepts every reader needs.
  • Admin is for creators using the Membership.io admin.
  • Build is for developers, with one group per module in the order the Modules page uses.
  • Agents covers the CLI and the product MCP server.
  • Reference holds the conventions and the generated endpoint reference.

​
Who these docs are for

Use these docs if you are building:
  • A creator dashboard that manages hubs, products, contacts, media, email, and community.
  • A member portal where contacts log in, view content, join spaces, and manage billing.
  • A backend integration that syncs contacts, provisions access, or starts checkout.
  • A CLI or automation that operates on a team’s data.

​
Current alpha note

The API has strong JSON:API foundations, but a few alpha-era endpoints still use legacy response or request shapes. These docs call out the important exceptions, and the generated OpenAPI reference remains the exact source for each endpoint.