Rumora

Status and polling

How thread and Find handles move from queued to live, and what get_status returns.

Every write returns a handle before the comment is live. post_comment and post_thread return a thread id. find_videos returns a Find job id. get_status accepts either id. There is no webhook. You poll.

curl -sS "$HOST/api/v1/status/ID_FROM_THE_LAST_CALL" \
  -H "Authorization: Bearer $TOKEN"

Reads do not count toward the 10 writes per minute limit. Wait a few seconds between polls.

When to stop (thread)

The JSON has "type": "thread".

  • Keep polling while identity is null or status is not live.
  • Stop when identity is an object. Then like or reply with those fields. See Comment identity.
  • If status is a failure, stop and read error. Do not like.

next_step is a sentence telling you the next call. Follow it.

When to stop (Find)

The JSON has "type": "find".

  • Keep polling while cards is missing or empty and status is not refunded.
  • Stop when cards has URLs. Copy a url, then call post_comment or post_thread. Find does not paste and does not post.
  • Stop when "status": "refunded". The search returned nothing and the Find credits came back. Change keywords and start a new job with a new idempotency_key.

How often

Poll every few seconds. Most comments go live in well under a minute. If identity never appears, open Threads in the web app and look up the same id.

Last updated on

On this page

Using an AI agent?

Copy the page as Markdown, or send the agent /llms.txt.