X user replies, one page
/api/v1/twitter/web/fetch_user_tweet_repliesOne page of an X user's Posts & replies tab, newest first: about 40 items per page. It holds every reply the user wrote to others (X search returns few of them), and each page also carries the posts being replied to: keep the items whose author.screen_name is the user's. It holds only some of the user's own posts; for those use /api/v1/twitter/web/fetch_user_post_tweet. The two tabs together can still miss a few posts: for every post of an account in a period, also run /api/v1/twitter/web/fetch_search_timeline with from:handle, since: and until:, and merge the three by post id. Pass data.next_cursor back as cursor for the next page. A provider 400 saying 'Request failed. Please retry' is TikHub's answer for a handle that does not exist, an account TikHub cannot read (even an active, verified one), an account with no posts, or an X path outage; the same input gets the same 400 again, so retry once at most before switching Endpoints. One request per call; TikHub bills the request whether or not data comes back, and an empty data envelope is reported as no result.