Skip to main content
Membership.io is multi-tenant. The main rule is simple: admin data belongs to a team, and member experiences belong to a hub.

​
Team-scoped admin routes

Admin routes include team_id in the path: 
/api/v1/teams/{team_id}/contacts
/api/v1/teams/{team_id}/hubs
/api/v1/teams/{team_id}/products
/api/v1/teams/{team_id}/files
When you use a team API key, the key is bound to exactly one team. A key minted for Team A cannot operate on Team B.

​
Hub-scoped member routes

Member-facing routes include hub_id or a hub slug: 
/api/v1/hub/{hub_id}/content
/api/v1/hub/{hub_id}/pages/home
/api/v1/hubs/{slug}
The backend checks live membership and access rules for protected hub resources. Do not assume that a contact token alone means the member can see every hub resource.

​
Common identifiers

IdentifierMeaning
team_idCreator-side tenant
hub_idMember destination
contact_idGlobal person identity
team_contact_idContact’s CRM record inside a team
product_idSellable item
price_idPayment option for a product
media_id or file_idUploaded media/file resource