X API | Twitter API comments user posts

SocialDataX read-only X API and Twitter API for public post search, details, Twitter comments, comment replies, user profiles, user posts, and replies posted by a user.

Apify users do not need to configure a SocialDataX API Key. The Actor owner configures SOCIALDATAX_API_KEY as an Apify secret.

User-post rows expose is_pinned (true / false) in Overview and User posts. An omitted field means the API did not provide it. The Actor preserves the returned order and pagination.

Support

If a run fails, you need higher limits, or you want to discuss a bulk data workflow, contact SocialDataX support:

• Website: https://socialdatax.com/ai?from=apify

Operations

• search_users: X / Twitter user search using keyword, with optional page_token, max_items, and auto_paginate.
• search_suggestions: X / Twitter keyword suggestions using keyword; returns up to max_items text rows in one request without pagination.
• search_posts: Search Posts using keyword.
• get_post_detail: Get Post Detail using post_id or post_url.
• get_post_comments: Get Post Comments using post_id or post_url.
• get_post_comment_replies: Get Post Comment Replies using post_id / comment_id.
• get_user_info: Get User Info using user_id or username or profile_url.
• list_user_posts: List User Posts using user_id or username or profile_url.
• list_user_replies: List replies posted by a user, including self-replies. Provide exactly one of user_id, username, or profile_url. To read comments under a specific post, use get_post_comments.

Pagination

List operations use page_token, max_items, and auto_paginate. Each requested page counts as one SocialDataX API request. Results are written to the default Apify Dataset and can be exported as JSON, CSV, Excel / XLSX, or JSONL.

If max_items or the Dataset budget cuts a page short, OUTPUT.warnings and the run log report the partial export. page_next_page_token advances to the next whole page and will skip unexported items on the current page. To retrieve those items, repeat the current page using its query_page_token and allow enough output budget for the full page. For list_user_replies, deduplicate saved replies by post_id.

For list_user_replies, keep the same user and identity field when continuing with page_next_page_token. Do not reuse tokens from list_user_posts or other operations. An empty page with a next-page token can be continued; an empty token ends pagination.

User replies

{
  "operation": "list_user_replies",
  "username": "elonmusk",
  "max_items": 20,
  "auto_paginate": false
}

Each reply is one Dataset item under the existing billing rules. post_id identifies the reply itself; reply_to_post_id identifies its parent post. Use the User replies Dataset view to see both IDs and the author.

Intermediate empty pages do not occupy Dataset rows during automatic pagination. If a run stops on an empty page with a continuation token, it writes an empty_page=true summary row so you can continue; that row follows the existing Dataset item billing rules. A terminal empty page writes no row.

Example input

{
  "operation": "search_posts",
  "keyword": "camping",
  "sort_type": "hot",
  "page_token": "",
  "max_items": 50,
  "auto_paginate": true
}

Billing

Ongoing use requires an Apify paid plan. Free-plan users get a limited SocialDataX API request trial.

Recommended Apify Pay per event setup:

• apify-default-dataset-item: $0.0005 / Dataset item
• apify-actor-start: keep Apify default $0.00005
• Pay per event + usage: off