Version
GET

List the connector directory

/v1/connectors in the Connectors API.

Every connector Subscriby knows, lane by lane, installable connectors first, each with its badges and, for a registered one, its whole manifest and the connect form. ?status= narrows to one lane.

curl https://api.subscriby.net/v1/connectors \  -H "Authorization: Bearer $SUBSCRIBY_TOKEN"

Cards come lane by lane, installable connectors first; within a lane the most installed connector comes first (installations, the number of projects running it today, uninstalled rows excluded) and the name breaks ties. The public and in-app directories offer the same order plus Newest (added_at) and Name, and filter on official, installable and category; a client sorts and filters on the same fields.

Lanes and badges

statusstatus_labelMeaning
availableAvailable NowA package is present and configuration offers it; installable is true.
betaExperimentalAvailable, and flagged so; a badge on the card, never a gate. installable is true.
pausedPausedSwitched off during an incident. Nothing new is installed and sends queue until it is back.
in_developmentUnder DevelopmentA package exists but configuration does not offer it yet (built, on staging, dark).
coming_soonComing SoonA roadmap entry with no package behind it: the card, the category and an eta sentence only.

badges are facts the platform stamps, never a package's own claim: official or community (who publishes it), new while the listing was added within the last sixty days, trending for the connector(s) creators installed most in the last thirty days. A coming_soon card carries none.

GET
/v1/connectors

The token must hold this ability, or the call is refused with 403.

Runs the same action from an agent, behind the same ability.

Authorization

bearerToken
AuthorizationBearer <token>

A personal access token minted on the dashboard under Settings, then Tokens, sent as Authorization: Bearer sbt_live_…. The token carries the abilities each endpoint lists under Requires ability and is frozen to one team.

In: header

Query Parameters

status?string

Narrow the directory to one lane: available, beta, paused, in_development or coming_soon. Omit for every lane. An unknown lane is 422 VALIDATION_FAILED naming the accepted values.

Responses

200OK

Array of ConnectorListingResource

401Unauthorized

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

403Forbidden

The token is valid but does not carry the ability this endpoint requires; error.context.required_ability names the one to grant. An endpoint that also checks who owns a row or which tier the account is on answers FORBIDDEN, TEAM_TIER_REQUIRED or CONNECTOR_TIER_REQUIRED with the same status, and says so in its own description.

422Validation failed

When status names no lane; error.context.accepted lists the lanes.

429Too many requests

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

How is this guide?

Last updated on