Skip to main content
GET https://xquik.com/api/v1/x/tweets/{id}/hidden-replies
Requested result counts are upper bounds for paid authenticated calls. Remaining credits may not cover the full page or ID list. If so, Xquik returns fewer results. If zero paid results are affordable, it returns 402 insufficient_credits.
1 credit per result returned · All plans from $0.00012/credit · Supports guest paid reads

Order and empty results

Use GET /x/tweets/{id}/hidden-replies for the replies a post’s author hid. X (Twitter) lists them under “Hidden replies” on the post. Rows arrive oldest first. The examples above save that order as hidden_position. The list also holds the replies to a hidden reply. Use inReplyToId to tell them apart from replies to the post. A post without hidden replies returns an empty list, not an error.
The last page looks the same. Stop paging when has_next_page is false. A post X does not have returns 404 tweet_not_found. Xquik charges nothing.

Which reply endpoint?

  • Use GET /api/v1/x/tweets/{id}/hidden-replies for replies the author hid.
  • Use GET /api/v1/x/tweets/{id}/replies for the replies X shows under a post.
  • Use GET /api/v1/x/tweets/{id}/thread for the conversation around a post.

Path parameters

Query parameters

Tweet result filters

These optional filters apply to tweets[] returned by this route. They keep the same hidden replies target. Xquik filters rows after it fetches each page. Selective filters can return fewer rows than an unfiltered page.See tweet filters for every filter. Common ones are fromUser, language, sinceDate, mediaType, minLikes, and hashtags.

Choose fields

Headers

Response

200 OK

400 Invalid tweet ID

{ "error": "invalid_tweet_id" } The tweet ID is empty or invalid.

401 Unauthenticated

Anonymous requests get WWW-Authenticate: Bearer and a guest wallet checkout action. This is not a Payment challenge. Missing or invalid API key.

402 Payment required

Account keys get account options. Guest keys get guest top-up only. No checkout starts automatically. Confirm any payment action.

502 X API unavailable

The read service returned an error. Retry after a short delay.

429 Rate limit exceeded

You exceeded your tier rate limit. Wait for the Retry-After header before retrying.

424 Dependency failed

The normalized v1 response contract can return 424 when the read service is unavailable.

Response examples

  • 400 { "error": "invalid_input", "message": "Invalid input. Check the request body." }
  • 401 { "error": "unauthenticated", "message": "Authentication required." }
  • 402 { "error": "insufficient_credits", "message": "Insufficient credits. Top up or subscribe to continue." }
  • 403 { "error": "api_key_paused", "message": "This API key is paused. Resume it at dashboard.xquik.com/api-keys to use it again." }
  • 404 { "error": "tweet_not_found", "message": "Tweet not found. Check the tweet ID." }
  • 424 { "error": "x_api_unavailable", "message": "X data source temporarily unavailable. Try again later." }
  • 429 { "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 }
  • 502 { "error": "x_api_unavailable", "message": "X data source temporarily unavailable. Try again later." }
  • 503 { "error": "x_api_unavailable", "message": "Xquik is busy right now. Retry shortly." }