REST API
Replies and insights
Read the thread under a post, answer it, hide what you do not want, and read the numbers.
Replies live under a publish, not under a workspace. Every call here takes the post the way the post routes do: the publish id you got from POST /v1/posts, the post's id on the channel, or an encoded link to it.
Posts on more than one channel
When one publish went out on several channels, each channel has its own copy with its own replies. Every call here works on one copy. It is the one accountId names, or the copy a channel link points to, or the one whose comment you answer (a reply id we know, such as a triggerRef from an automation run). With none of these a read still picks one, and the answer says which in accountId and platform and lists the rest in otherAccounts. A write without them, or with two that point at different copies, sends nothing and answers 400 account_required with accounts [{ id, platform, handle }]; channels that cannot do that action are left out and the message says why.
GET/v1/posts/{id}/replies
The reply thread under a published post.
| Name | Type | Description |
|---|---|---|
accountId | query | Which channel's copy to read, on a post that went to more than one channel. Omit and the answer says which copy it read. |
POST/v1/posts/{id}/replies
Reply to the post, or to a reply under it.
| Name | Type | Description |
|---|---|---|
contentRequired | string | Reply text. On Threads, Bluesky and X a reply is a post, so that channel's character limit applies; a longer reply answers 422 content_too_long with limit and actual and nothing is created. |
replyTo | string | A reply id from the thread, or a link to that comment. Omit to answer the post itself. |
wait | boolean | Hold the response until the reply is out, up to 10 seconds. Answers 200 with the post when it settles, otherwise 202 with next. |
accountId | string | Which channel's copy, on a post that went to more than one channel. A connected account id, from list_accounts or a read of this post. |
Nested replies
Leave replyTo out and you answer the post. Pass a reply id and you answer that reply, one level deeper. There is no separate endpoint for it. The same call does both.
# answer the post
curl -X POST https://api.uplika.com/v1/posts/post_01H.../replies \
-H "authorization: Bearer $UPLIKA_KEY" \
-H "content-type: application/json" \
-d '{"content":"Thanks for reading"}'
# answer a reply — one level deeper
curl -X POST https://api.uplika.com/v1/posts/post_01H.../replies \
-H "authorization: Bearer $UPLIKA_KEY" \
-H "content-type: application/json" \
-d '{"content":"Good question","replyTo":"17901234567890123"}'Acting on other people's posts
Replies, likes and following are how a blog grows, and most of that happens on other people's posts. These three calls take the target as ownerHandle plus externalId (for Naver, the blog id and the logNo from the link), or postId for your own post. You always act as the connected account; ownerHandle is who you act on. Naver Blog is the only channel that supports them today, and the extension does the work in your browser like it does for publishing. Liking is a toggle on Naver, so we read the state first and never turn a like off. Naver silently ignores liking your own post, which comes back as naver_not_allowed.
POST/v1/engagement/like
Like a post, or a reply under it. Idempotent; there is no unlike.
| Name | Type | Description |
|---|---|---|
postId | string | Your own publish. Or pass ownerHandle and externalId instead. |
ownerHandle | string | Who owns the post. Naver Blog: the blog id. |
externalId | string | The post's id on the channel. Naver Blog: the logNo from the link. |
replyId | string | A reply id from the thread to like that reply instead of the post. |
accountId | string | With postId: which channel's copy of your post, and that account acts. With ownerHandle: which connected account acts, only needed with more than one account on that channel. |
POST/v1/engagement/reply
Reply to a post that is not yours (Naver Blog). No publish record is created.
| Name | Type | Description |
|---|---|---|
ownerHandleRequired | string | Who owns the post. |
externalIdRequired | string | The post's id on the channel. |
contentRequired | string | Reply text. |
replyId | string | Reply under this reply instead of under the post. |
secret | boolean | Naver Blog: a secret comment only the blog owner can read. |
POST/v1/engagement/follow
Follow an account (Naver Blog: add as neighbor). mutual sends a request the other side accepts, and that request needs a message. group puts the blog in one of your neighbor groups by name.
| Name | Type | Description |
|---|---|---|
ownerHandleRequired | string | The account to follow. Naver Blog: the blog id. |
mutual | boolean | Naver Blog: send a mutual-neighbor request instead. Comes back pending until accepted. |
message | string | Required with mutual: shown to the other blog. Up to 400 characters. |
group | string | Naver Blog: the name of one of your neighbor groups, as it appears on Naver. Leave it out for Naver's default group. Up to 100 characters. Uplika does not create groups: a name the blog does not have answers naver_follow_group_missing, and an older extension answers 422 extension_outdated. |
accountId | string | Which connected account acts. |
| Name | Type | Description |
|---|---|---|
queryRequired | string | The topic, 1 to 100 characters. The server searches Naver's blog search for the newest posts on it and groups them by blog. |
mutualRequired | boolean | The kind of request you will send with follow. true leaves out mutual neighbors, requests already sent and refusals, and keeps one-way neighbors; false keeps only blogs not linked at all. |
days | number | Keep blogs with a post on the topic within this many days, counted back from today. 1 to 30, default 30. |
accountId | string | Which connected Naver Blog to check against. Only needed with more than one. |
| Name | Type | Description |
|---|---|---|
neighbors | string | "mutual" (default) leaves out posts from blogs known to be one-way neighbors and keeps posts whose relation is unknown (mutual: null). "all" keeps every neighbor's post. |
accountId | string | Which connected Naver Blog to read as. Only needed with more than one. |
POST/v1/replies/{replyId}/hide
Hide a reply on the channel, or show it again.
| Name | Type | Description |
|---|---|---|
postIdRequired | string | The publish the reply sits under. |
hide | boolean | true hides it, false shows it again. Default true. |
accountId | string | Which channel's copy, on a post that went to more than one channel. A connected account id, from list_accounts or a read of this post. |
DELETE/v1/replies/{replyId}
Delete a comment for good. Unlike hide, this cannot be undone, and which channels have it at all is in features on GET /v1/platforms.
| Name | Type | Description |
|---|---|---|
postIdRequired | string | The publish the reply sits under. |
accountId | string | Which channel's copy, on a post that went to more than one channel. A connected account id, from list_accounts or a read of this post. |
GET/v1/posts/{id}/insights
Views, likes, replies, reposts, quotes and shares.
| Name | Type | Description |
|---|---|---|
accountId | query | Which channel's copy to read, on a post that went to more than one channel. Omit and the answer says which copy it read. |
{
"views": 1240,
"likes": 38,
"replies": 6,
"reposts": 2,
"quotes": 1,
"shares": null
}Metrics on X
Every metrics read on X is paid from X credits, so metrics are switched on per X connection by the person on the Connections page, and they are off by default. While they are off, this answers 200 with noteCode x_analytics_not_enabled, no numbers and nothing charged. While they are on, X is read and charged the insights price at most once per post per UTC day; later calls that day return the same numbers for free. If the balance is too low, this answers 402 x_credits_insufficient with topUpUrl. GET /v1/posts/{id}/thread (open_post) reads the same metrics: there a low balance leaves metrics null and the text and replies still come back.
Common questions
How do I reply to my own post?
Call reply with the publish id and leave replyTo out. That answers the post itself, which is how a thread starts.
How do I nest a reply under another reply?
Pass the reply's id as replyTo on the same call. There is no separate endpoint; one call does both depths.
Which numbers can I read?
Views, likes, replies, reposts, quotes and shares. Some come back null while the platform is still counting, and null means unknown, not zero.