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."
}
}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.