connections_get
Poll a connection started with connections_create: pending → completed (then list destinations) or failed (reason included).
Poll a connection started with connections_create: pending → completed (then list destinations) or failed (reason included). Poll every few seconds while the human finishes the browser consent.
Input
| Field | Type | Required | Description |
|---|---|---|---|
organization | string | no | Organization slug to act in (see organizations_list). Optional: API keys are bound to one organization; OAuth connections default to your active organization. |
connect_id | string | yes | Connection id from connections_create |
Result
JSON on success. A refusal comes back as an error prefixed with its code (NOT_FOUND, FORBIDDEN, TOO_MANY_REQUESTS, …) and a message written to be acted on — read it before retrying.
The same operation elsewhere
This tool and the REST operation connectionsGet run the same guarded procedure the dashboard uses — same permissions, same validation, same tenant isolation.
connections_create_with_credentials
Connect a social account that has NO browser consent screen — today that is Bluesky, which authorizes with a handle plus an app password.
connections_destinations
After a connection completes: the publishable destinations (profile, pages) the new grant can post to, with `connected` marking ones already present.