Connectors API

A Subscriby project runs on connectors: the platforms it gates access on, sends messages through and takes payments from. The directory these endpoints serve is the same one the dashboard and the marketing site render, so a client reads one document and knows which connectors exist, which a creator may install today, what each can do, and exactly which fields connecting one asks for. The manifest is served whole because the creator apps render the connect form from it: no client has to know what a "bot token" is before the connector says so.

The catalogue is the same for every creator and never carries a credential. A project's installations are what the Connectors tab lists: every connector set up on the project, live and standby, with its state and health.

EndpointsCopy Anchor Link

Related

Resources APIThe places a project gates on its connectors.connector.* eventsconnector.*.Ability Catalogproject-connector:*.Error CodesEvery write here answers 404 RESOURCE_NOT_FOUND with reason: unknown_connector for a key that names no connector, and 404 CONNECTOR_NOT_INSTALLED for one the project does not run.Resources Referencesubscriby://connectors/catalog carries the whole directory for an agent to read at session start.