> ## Documentation Index
> Fetch the complete documentation index at: https://docs.member.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Membership.io API

> Build creator dashboards, member portals, integrations, and automation against Membership.io.

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.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Make your first authenticated request and learn the request shape.
  </Card>

  <Card title="Mental model" icon="blocks" href="/concepts/mental-model">
    Understand teams, hubs, contacts, memberships, and access.
  </Card>

  <Card title="Authentication" icon="key-round" href="/concepts/authentication">
    Choose between platform JWTs, contact JWTs, and team API keys.
  </Card>

  <Card title="API reference" icon="braces" href="/reference/overview">
    Browse the generated OpenAPI reference and full endpoint inventory.
  </Card>
</CardGroup>

## 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.