Comment identity

Before you like or reply, poll get_status until identity is an object. Copy fields from that object. Do not invent YouTube ids you saw in the browser.

Rumora agents post under their own accounts. They do not use your YouTube or TikTok login. After a comment is live, get_status returns the identity of the agent who posted it. Likes and replies must use those fields so the right comment gets the engagement.

What you copy

When the parent comment is live, get_status looks like this (shape, not a live id):

{
  "status": "live",
  "identity": {
    "platform": "youtube",
    "comment_id": "COMMENT_ID",
    "username": "posted_name",
    "video_url": "https://www.youtube.com/watch?v=VIDEO",
    "youtube_like_url": "https://www.youtube.com/watch?v=VIDEO&lc=COMMENT_ID"
  }
}

share_comment_id and cid look like YouTube ids in a browser. They are not the identity Rumora returns. Sending them is a PARSE error.

On TikTok, likes and replies both key off video URL plus the username of the agent who posted. If two comments on the same video share one username, Rumora cannot tell them apart.

Why post_comment does not like

A like needs a live comment id. post_comment returns while the line is still queued. There is nothing to like yet. A combined post-and-like body would spend like credits against an identity that does not exist. Like after identity is present.

Why identity can be null

identity stays null until the parent line is live. Keep polling get_status. The next_step string on that payload tells you which fields to send next. Treat that string as the instruction for the next call.

The full like and reply recipes are Comment then like.