Projects API

A project is the container for one membership business: its plans, its members and their subscriptions, its payment methods, the resources a purchase unlocks and the connectors it runs on. A team can hold several, each with its own portal at a handle of its choosing, its own terms and privacy links, artwork and public-metrics switch. A project has no platform of its own: it installs connectors, and the places those connectors gate become its resources.

The endpoints create, read, update and delete projects, and offer archive and restore as actions separate from update. Archiving flips active off so the portal stops selling while every plan, member and payment method is kept; restoring switches it back on. Delete removes the project and everything under it, so prefer archiving to pause intake without losing history. A custom handle needs the account tier that unlocks it, and changing it moves the portal URL at once.

A token minted with scope:project entries sees only those projects, and any project outside the token's team or scope is a 404 RESOURCE_NOT_FOUND. Every change announces itself as a project.* event; connecting and disconnecting a connector emits connector.* events from their own flows rather than from here.

EndpointsCopy Anchor Link

Related

Plans APIA plan is what a project sells: the price, the currency, the billing cycle or the dated windows, the eligibility rules and the resources a purchase unlocks.Connectors APIThe platforms a project runs on.Ability CatalogEvery ability string a token can carry, what enforces it on the API and the MCP server, and how to pick the right ones when minting.Webhook Events APIA read-only polling endpoint that surfaces the most recent webhook deliveries for a given event type.project.* eventsWhat the endpoints below announce; connector.connected and connector.disconnected come from the connect and disconnect flows, not from here.