Check Reply

Checks whether a user has replied to a tweet. It makes a single read of the user's Replies tab and accepts a reply to this post or to anything in its thread. One read covers roughly the 20 to 25 newest replies the account wrote, so call this right after the user replies, which is also why it answers in about a second instead of paging through a history. The response carries a scanned object with the size of that window. Optionally verify that the reply tags a minimum number of friends (common in giveaway campaigns). The tweet author's @mention is automatically excluded from the tag count. If that read cannot be completed the endpoint answers 503 with a Retry-After header rather than reporting that the user did not reply, and the call is not billed. If it comes back empty with no end-of-timeline marker, which is what an account we cannot read looks like, you get an unbilled 422 with code REPLIES_UNREADABLE instead, and for five minutes that handle is answered from memory without calling X. A page that does carry tweets but none of them the user's own is a normal negative: this tab also ships the posts the account replied to. No connected X account needed (uses pool accounts).

GET/v2/tweets/:tweetId/check-replyCheck if a user has replied to a tweet.

Parameter	Type	Required	Default	Description
tweetId	string	required	—	Tweet ID or URL (path parameter)
username	string	required	—	Username to check, with or without @ (query parameter)
min_tags	number	optional	—	Minimum friend tags required (0-20, default 0 = no check)

BASH

# Check reply with 2 friend tags required
curl "https://xcrop.io/api/v2/tweets/1893045621038174208/check-reply?username=elonmusk&min_tags=2" \
  -H "Authorization: Bearer $XCROP_API_KEY"

ResponseJSON

{
  "data": {
    "replied": true,
    "verified": true,
    "tags_required": 2,
    "tags_found": 3,
    "tags_met": true,
    "replyTweet": {
      "id": "1893112345678901234",
      "text": "@author Great post! @friend1 @friend2 @friend3",
      "createdAt": "Mon Mar 02 10:30:00 +0000 2026"
    },
    "tweetId": "1893045621038174208",
    "username": "elonmusk",
    "checkedAt": "2026-03-07T15:00:00.000Z",
    "scanned": { "items": 40, "own": 21 }
  },
  "meta": { "latency_ms": 291 }
}

When min_tags is 0 or omitted, verified equals replied. When min_tags is set, verified is true only if the user replied AND tagged enough friends.

More in Interaction Check

Full documentation with search: xcrop.io/docs