Skip to main content
Membership.io is organised into modules. Each module is one product area, with its own pages in the admin, its own guides, and its own set of tags in the generated API reference. The modules appear in the same order here, in the Build tab, and in the endpoint reference, so once you know the order you can find a feature anywhere in these docs.
The tag lists on this page are maintained by hand. The endpoint inventory is generated from the API and lists every route under every tag.

​
Account and team

Creator-side sign-in, users, teams, roles and permissions, and the team API keys that integrations and the CLI use.

​
Hubs

A hub is the branded member destination. Create one, manage it, give it a custom domain, and build it out from a template.

​
Members and auth

How a contact becomes a member: registration, login, magic links, external sign-in providers, verified-domain SSO, and using a hub as an identity provider for your own apps.

​
Contacts and audience

The team’s CRM: contacts, tags, custom attributes, activity, and the segments built from them.
  • In the admin: Manage contacts
  • API guides: Tags, attributes, activity, and segments
  • Tags: contacts-admin, tags-admin, tags-assignments, contact-attributes-admin, contact-attributes-admin-hub-config, contact-attributes-admin-values, contact-attributes-portal, activity-admin, activity-portal, segments-admin, segments-hub

​
Content and pages

The content tree members learn from, the pages a hub renders, the access rules that decide who sees what, saved items, and achievements.

​
Media

Upload, organise, attach, transcribe, and search files, from the Library in the admin, the CLI, or the API.
  • In the admin: the Library, covered in Media workflow
  • API guides: Media workflow · Find file usages
  • Tags: media-admin, media-admin-folders, media-admin-attachments, media-admin-hub-media, media-member, media-member-hub-media, media-public, media-search, media-transcript, admin-transcription

​
Commerce

Products, prices, checkout sessions, orders, subscriptions, refunds, and the access a purchase grants.

​
Community

Spaces, discussions, comments, messages, profiles, follows, moderation, search, hub events, notifications and push, and the live event stream.
  • API guides: Community workflow · Notifications inbox · Realtime (SSE)
  • No guide yet: hub events
  • Tags: community-spaces-admin, community-spaces-member, community-discussions, community-discussions-admin, community-anon, comments, comments-admin, community-conversations, community-messages, community-dm-candidates, community-dm-capabilities, community-mention-candidates, community-profile-me, community-avatar-upload, community-banner-upload, community-attachment-upload, community-external-video-embed, community-directory, community-member-activity, community-hub-member-counts, community-moderation, community-moderation-admin, community-search, follows, notifications, web-push, hub-events, hub-events-admin, hub-events-anon

​
Email and automations

Sending configuration, templates, drip campaigns, suppressions and unsubscribe, event-driven automations, and outbound webhooks.
  • API guides: Email and drips · Automations · Webhooks
  • Tags: email-config, email-stats, email-suppressions-admin, email-suppressions-hub, email-unsubscribe, email-webhooks, drip-campaigns, automations, webhook-endpoints

​
Analytics and monitoring

Hub analytics, the alerts that need a team owner’s attention, the platform-admin alert surface, and runtime discovery.

​
Agents

The MIO CLI drives every module above from a terminal, and the member.dev MCP server lets an AI assistant work on them through a catalog of tools behind an OAuth consent screen.