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
identityisnullorstatusis notlive. - Stop when
identityis an object. Then like or reply with those fields. See Comment identity. - If
statusis a failure, stop and readerror. 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
cardsis missing or empty andstatusis notrefunded. - Stop when
cardshas URLs. Copy aurl, then callpost_commentorpost_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 newidempotency_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