logo
FR

Twitter (X) Comments Scraper

Collect public replies from Twitter post URLs with the source post, reply author, content, timestamps, media links, and engagement details.

Collecte de donnéesSocial MediaX (Twitter)Posts
Développeur
YiJacobJohnRaku
Tarifs
0,0003 $US / enregistrement
Dernière mise à jour
2026-09-10

Aperçu

Twitter (X) Comments Scraper turns known public post URLs into structured reply records that are ready to review, filter, and compare. Each record connects one reply to its source post and preserves the post and reply links, authors, text, publication times, media links, visible engagement counts, deletion indicator, and any collection message.

This dataset helps teams move beyond a post-level engagement total and inspect the conversation underneath it. Because each reply stays linked to the source post and the replying account, the results can support qualitative conversation review, visible-audience research, response-pattern analysis, and evidence gathering around a defined set of posts.

Data notes

Records come from publicly accessible Twitter conversations and reflect what the collector could see when the run took place. Each record represents one collected reply to one submitted source post, and the reply URL is used to remove duplicate records across retrieved result pages. Post and reply timestamps retain the source's displayed UTC offset. Like, retweet, reply, bookmark, and view counts are snapshots reported at collection time and can change afterward; they are preserved as reported text rather than recalculated values. Multiple source-post image addresses may be joined with vertical bars, while an empty reply-image value means no image was reported for that reply. Private, restricted, deleted, and sign-in-only content may not be available.

What the results look like

Each record is one collected public reply linked to its source post:

Reply author nameReply contentReply timestampReply URLReply likesReply views
ALT_uscis@smutoro @Meta @instagram @facebook The COVID era was THE TRUMP ERA YOU MORONTue Aug 27 13:49:59 +0000 2024https://x.com/ALT_uscis/status/182842975610829645213713
ExampleResponderA short public response to the source post.Tue Aug 27 14:02:10 +0000 2024https://x.com/ExampleResponder/status/18284328000000000004128

The output also includes “Source post URL,” “Source post ID,” “Post author name,” “Post author URL,” “Post timestamp,” “Post content,” “Post image URLs,” “Post likes,” “Post retweets,” “Post replies,” “Post bookmarks,” “Reply author URL,” “Reply image URL,” “Reply retweets,” “Nested replies,” “Deletion indicator,” and “Collection message.”

Use cases

  • For conversation analysis, group records by “Source post URL” and review “Reply content” to identify recurring questions, objections, claims, and themes beneath each post.
  • For visible-audience research, compare “Reply author name” and “Reply author URL,” then use “Reply URL” to inspect the original public context.
  • For reply-engagement comparisons, evaluate “Reply likes,” “Reply retweets,” “Nested replies,” and “Reply views” together to identify which collected responses drew more visible interaction.
  • For post-to-reply context review, compare “Post content” with “Reply content” and their respective timestamps to preserve the relationship between a statement and the responses it received.

Périmètre et limites

Each run accepts 1 to 100,000 public Twitter post URLs and can request up to 100,000 replies per post; retrieval is capped at 10,000 returned records per run.

  • Adapté pour
  • Use it when you need reply-level records for one or more known public Twitter posts.
  • Use it for conversation analysis, respondent discovery, reply engagement comparisons, or evidence collection around specific posts.
  • À ne pas utiliser pour
  • Do not use it to discover posts by keyword or hashtag because it starts from known post URLs.
  • Do not use it for private, deleted, restricted, or sign-in-only conversations because only content visible to the collector is covered.

Gestion des échecs

Comportement en cas d'échec et de nouvelle tentative déclaré par le développeur. Nous vous recommandons de l'inclure dans votre prompt système lors de l'intégration.

  1. 1If a run stops before completion, retry the same small input once; if it stops again, use fewer post URLs or request fewer replies.
  2. 2An empty result can mean the post has no visible replies, the URL is unavailable, or access was temporarily limited; verify the post URL and retry later.

Entrée

Paramètres requis pour appeler cette App, générés à partir de l'input.schema du manifest.json.

  • Twitter post URLstweet_urlsRequisarray<string>
    Public Twitter or X post URLs whose replies should be collected. Enter 1 to 100,000 URLs per run.
    Nombrejusqu'à 100000 élémentsExemple["https://x.com/smutoro/status/1828297507484438722"]
  • Replies per postreply_limitFacultatifinteger
    Maximum number of replies to request for each post, from 1 to 100,000. When omitted, the collector decides the limit; set it explicitly when a predictable depth is important.
    Plage1–100000

Sortie

Structure des champs d'un enregistrement, générée à partir de l'output.schema du manifest.json.

  • Source post URLtweet_urlstring
    Direct address of the source Twitter post.
    Exemplehttps://x.com/smutoro/status/1828297507484438722
  • Source post IDtweet_idstring
    Identifier of the source Twitter post.
    Exemple1828297507484438722
  • Post author nametweet_author_namestring
    Display name of the account that published the source post.
    ExempleStephen Mutoro
  • Post author URLtweet_author_profile_urlstring
    Direct address of the source post author's profile.
    Exemplehttps://x.com/smutoro

Exemple de données

Généré à partir d'output.schema. Les champs sans valeur d'exemple utilisent des espaces réservés structurels.

output.example
{
  "tweet_url": "https://x.com/smutoro/status/1828297507484438722",
  "tweet_id": "1828297507484438722",
  "tweet_author_name": "Stephen Mutoro",
  "tweet_author_profile_url": "https://x.com/smutoro",
  "tweet_posted_at_utc": "Tue Aug 27 05:04:28 +0000 2024",
  "tweet_content": "The @Meta, @instagram and @facebook owner Mark Zuckerberg says he regrets working with the Biden-Harris administration to censure information online during the #Covid19 era https://t.co/G8nKVLDDPG",
  "tweet_image_urls": "https://pbs.twimg.com/ext_tw_video_thumb/1828297475221774336/pu/img/dMCF64ISghcByCeH.jpg|https://pbs.twimg.com/media/GV9q30sWwAAU7cU.jpg|https://pbs.twimg.com/media/GV9q3xVXAAEzT4Y.jpg",
  "tweet_likes": "212",
  "tweet_retweets": "93",
  "tweet_replies": "52",
  "tweet_bookmarks": "89",
  "comment_url": "https://x.com/ALT_uscis/status/1828429756108296452",
  "comment_author_name": "ALT_uscis",
  "comment_author_profile_url": "https://x.com/ALT_uscis",
  "comment_timestamp": "Tue Aug 27 13:49:59 +0000 2024",
  "comment_content": "@smutoro @Meta @instagram @facebook The COVID era was THE TRUMP ERA YOU MORON",
  "comment_image_url": "",
  "comment_likes": "13",
  "comment_retweets": "0",
  "comment_replies": "2",
  "comment_views": "713",
  "is_deleted": "False",
  "error_message": ""
}

Intégration

Cette App peut être intégrée via MCP, API, SDK ou export de fichiers — tous les canaux partagent les mêmes capacités et la même tarification. Chaque requête s'authentifie avec l'en-tête Authorization: Bearer à l'aide d'une API Key (longue durée, créée dans la console Data Hub) ; les clients MCP peuvent aussi se connecter via OAuth, sans clé. D'autres options comme la CLI et Skill arrivent bientôt. Cette App s'exécute de manière asynchrone et peut être annulée en cours de route : Après l'annulation, l'exécution s'arrête. Les enregistrements déjà livrés sont conservés et facturés.

Avec MCP (Model Context Protocol), vous pouvez appeler cette App directement depuis des clients IA comme Claude et Cursor. Choisissez votre client et votre mode d'authentification, puis copiez la config ci-dessous.

Config du client

Remplacez la valeur après Bearer par votre API Key longue durée. Fonctionne dans n'importe quel client, en CI ou en environnement sans navigateur.

mcpServers config
{
  "mcpServers": {
    "octoparse_datahub": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=YiJacobJohnRaku/tweets-comments-scraper-by-search-result-url",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}
Voir mes API Keys →

Laissez l'IA tout configurer pour vous

Vous ne voulez pas modifier les configs à la main ? Copiez le prompt d'installation et collez-le dans n'importe quel client IA — il effectuera la configuration à sa manière. (Le prompt demande à l'IA de vous réclamer votre API Key, afin que les identifiants ne finissent jamais dans l'historique de conversation ni dans des configs partagées.)

detail.access.mcp.composeHint

Tarifs

returned comment record

Facturé selon le nombre d'enregistrements renvoyés avec succès. Les exécutions échouées ne sont pas facturées.

0,0003 $US/ enregistrement

Plusieurs événements de facturation se cumulent indépendamment. Voir chaque élément pour les détails. Les exécutions échouées ne sont pas facturées.

Voir les crédits

Essayer maintenant

Renseignez les paramètres et lancez l'exécution — les résultats proviennent d'un appel réel.

Exemple
Les paramètres sont validés par rapport à l'input.schema avant la soumission
0,0003 $US / enregistrement