Resources API

Resources are what a plan unlocks: a place a connector gates (a channel, group or supergroup on Telegram today; each connector's own kinds as it launches) or a manually-tracked perk such as a PDF, a token or a URL. The REST API reads every resource, creates manual perks, and asks the connector to link a place; it never attaches a place itself.

A place is linked only through its connector, which proves the installation administers it before the resource exists. The link-request endpoint starts that conversation; the REST and MCP surfaces accept no place identifier, so a token can never attach an arbitrary place.

EndpointsCopy Anchor Link

Related

Connectors APIEach connector's resource_kinds, with the labels, grant mode and plan shapes of every kind.ResourcesAdd the places your connectors gate and the manual perks a plan grants, and decide what a subscriber actually gets when they pay.Webhook Events APIA read-only polling endpoint that surfaces the most recent webhook deliveries for a given event type.project.* eventslinked fires when the connector finishes a link request, and updated also fires when a recovery swap moves the place (changes.space_id); the endpoints below announce their own changes.