Connections API
Connections API
Link social accounts to a LynCut profile through managed OAuth — publishing jobs target these connections.
Connections are authorized social accounts (YouTube, TikTok, Facebook, X, LinkedIn, Telegram). The API manages the OAuth handshake, token storage, refresh, and scope validation — publishing jobs just reference a connectionId.
OAuth flow
- GET /v1/connections/{provider}/connect redirects the user to the provider consent screen.
- The provider returns to /v1/connections/{provider}/callback; LynCut stores encrypted tokens.
- GET /v1/connections lists active connections with scopes and expiry.
- DELETE /v1/connections/{id} revokes access and removes stored tokens.
Telegram is not OAuth — bots connect via POST /v1/connections/telegram/connect with a bot token instead.
Connection states
| Status | Meaning |
|---|---|
| active | Token valid — usable for publishing |
| expired | Refresh failed — reconnect required |
| revoked | User revoked access on the provider side |
| error | Provider rejected the token (scope change, ban) |
Was this page helpful?