Getting started
Connecting channels
How a social account becomes something you can publish to.
Connecting happens in the dashboard, not over the API. The channel's OAuth screen has to be seen by a person.
Once connected, the account shows up in GET /v1/accounts with an id. That id is what publishing takes.
GET/v1/accounts
Once connected, the account shows up in GET /v1/accounts with an id. That id is what publishing takes.
{
"data": [
{
"id": "acc_01H...",
"platform": "threads",
"handle": "uplika_official",
"displayName": "uplika",
"status": "active"
}
]
}
// νλλ μμΌλ©΄ μ΄λλ‘ κ°μΌ νλμ§ κ°μ΄ μ¨λ€. μμΌλ©΄ μ΄ μΉΈμ μμ μλ€
{
"data": [],
"next": {
"action": "connect_channel",
"url": "https://uplika.com/en/dashboard/connections",
"message": "No channel is connected yet. Open that link, connect one, then try again."
}
}Sending a connection link
When an account belongs to someone else, such as a client, create a link and send it to them. They open it on their own device, sign in to the channel there, and the account lands in your workspace. They don't sign up for Uplika and don't share a password with you. GET /v1/platforms lists, under connectInvite, which channels a link can connect today. Channels whose posts are written by the Uplika browser extension are never connected from a link.
POST/v1/connect-invites
Create a connection link for the workspace. The url is in this response only: we keep a hash of it, so it cannot be read back. A channel a link cannot connect yet answers 400 invitation_channel, a channel that is never connected from a link answers 400 invitation_bridge, and past the daily cap it answers 429 invitation_limit.
| Name | Type | Description |
|---|---|---|
platforms | string[] | Required. Channel names whose connectInvite in GET /v1/platforms has a path with open: true. |
senderName | string | Required. Your name or your agency's. Your client sees it on the link page. |
note | string | Optional. A short message shown on the link page. |
locale | "en" | "ko" | Optional, defaults to en. The language of the link page. |
{
"id": "ci_...",
"workspaceId": "ws_...",
"url": "https://uplika.com/en/connect-invite/...",
"expiresAt": "2026-11-13T09:00:00.000Z",
"platforms": ["threads", "youtube"]
}GET/v1/connect-invites
Links created in the last 30 days, with status (open, expired or revoked) and, for each channel, the account connected from the link. The url is not in the list.
POST/v1/connect-invites/{id}/revoke
Cancel a link. Channels not connected yet can no longer be connected from it. Accounts already connected stay until you disconnect them.
Common questions
Can I connect a channel over the API?
No, and that is on purpose. The channel's own OAuth screen has to be seen by a person, so connecting happens in the dashboard and the API only sees the result.
Why does one of my channels say expired?
Its token could not be refreshed. We renew them in the background, and when that fails the account is marked expired so publishing is refused up front instead of failing halfway through.
Which channels can I connect right now?
Threads. Instagram, YouTube and Facebook are listed with status coming so you can build against them, and publishing to one is refused with platform_not_available rather than dropped quietly.