EN

Twitter Detail

Submit up to 200 Twitter post IDs and retrieve public post, account, engagement, and media details

Developer
Pricing
From $0.0015 / record
Last updated
2026-09-18

Overview

Public Twitter post details bring together the visible text, author identity, engagement snapshot, and media references for posts you already know. This Data App turns a batch of Twitter post IDs into consistent records that are ready for review, comparison, enrichment, or storage.

Instead of opening posts one by one and copying what is visible, teams can use the result as a structured research dataset. It is especially useful when a shortlist of posts has already been identified and the next step is to compare messaging, author context, publishing patterns, or public engagement.

Data notes

The data covers publicly available Twitter post details for the supplied post IDs. Each valid, deduplicated post ID returns at most one record, identified by Post ID. Invalid, duplicate, deleted, private, or login-only posts may return no record.

Like count, Comment count, View count, Quote count, Retweet count, Follower count, and related values are snapshots observed at collection time and may change later. Count fields are kept in the source text form. Post text, Image URLs, and Video URLs are also retained as source text. Published at and Collected at preserve source timestamps without inferring a timezone.

What the results look like

Each record represents the public details captured for one Twitter post.

Post IDAccount nameLike countContent typePublish locationPublished at
1034243881263542272ヒビトラ11video日本 日本海側2018-08-28T08:58:51
2090251737974059102AUTO.AE — Cars for sale0photoDubai2026-08-20T09:37:03

Additional values include account identifiers and profile links, media URLs, the full post text, collection timestamps, and the submitted post ID.

Use cases

  • Compare Like count, Comment count, Quote count, and Retweet count to identify posts with stronger visible engagement.
  • Review Post text, Content type, Image URLs, and Video URLs to classify creative themes and media formats.
  • Use Account name, Account ID, Account home URL, and Account handle to add author context to a selected post set.
  • Compare Published at, Collected at, Post URL, and Publish location across repeated collections to monitor availability and posting patterns.

Scope and boundaries

Each run accepts 1-200 Twitter post IDs; every valid deduplicated post ID returns at most one publicly available detail record.

  • Good for
  • Use when you need detailed public metadata and engagement snapshots for a known set of Twitter post IDs
  • Use when you need up to 200 post detail records in one background task
  • Do not use for
  • Do not use to discover posts by keyword, hashtag, or account; supply known Twitter post IDs
  • Do not use for private, deleted, or login-only posts

Failure handling

Failure and retry behavior declared by the developer. We recommend including it in your system prompt when integrating.

  1. 1Retry temporary task or service failures with the same post IDs
  2. 2If only part of the task succeeds, use the returned records and retry the missing post IDs
  3. 3An empty result can mean that a post ID is invalid, duplicated, unavailable, or no longer public

Input

Parameters required to call this App, generated from the input.schema in manifest.json.

  • Twitter post IDspost_itemsRequiredarray<object>
    Add 1-200 entries. In each entry, put the Twitter post ID in the Post ID field; invalid, duplicate, or inaccessible posts may return no record.
    Itemsup to 200 itemsExample[{"kw":"1034243881263542272"}]

Output

Field structure of a single record, generated from the output.schema in manifest.json.

  • Account avatar URLaccount_avatar_urlstring
    The account avatar image URL returned for this post.
    Examplehttps://pbs.twimg.com/profile_images/2080063431563149312/sZKFeQPr_normal.jpg
  • Follower countaccount_fans_countstring
    The account follower count kept in the source text form.
    Example850
  • Account home URLaccount_home_urlstring
    The public Twitter profile URL of the author.
    Examplehttps://twitter.com/eCxIgvhloBVcT1C
  • Account IDaccount_idstring
    The numeric Twitter account ID returned with this post.
    Example887883841485946882

Sample data

Generated from output.schema. Fields without a sample value use structural placeholders.

output.example
{
  "account_avatar_url": "https://pbs.twimg.com/profile_images/2080063431563149312/sZKFeQPr_normal.jpg",
  "account_fans_count": "850",
  "account_home_url": "https://twitter.com/eCxIgvhloBVcT1C",
  "account_id": "887883841485946882",
  "account_name": "ヒビトラ",
  "biz_id": "1034243881263542272",
  "collect_count": "0",
  "comment_count": "0",
  "content_id": "1034243881263542272",
  "content_long_url": "https://pbs.twimg.com/ext_tw_video_thumb/1034243424356978694/pu/img/2crGII0nH74rMomk.jpg;",
  "content_sec_id": "eCxIgvhloBVcT1C",
  "content_text": "日曜日の全日本ジムカーナ。\nNSX &amp;RX-7FD3S動画。\nイオックスアローザで撮影。 https://t.co/it4iuRwsiy",
  "content_type": "video",
  "content_url": "https://twitter.com/eCxIgvhloBVcT1C/status/1034243881263542272",
  "crawl_time": "2026-08-27T14:17:06",
  "cur_id": "6a8fd66397a2800ddeba8757",
  "forward_count": "1",
  "image_urls": "<image_urls>",
  "is_forward": false,
  "keyword_list": "1034243881263542272",
  "like_count": "11",
  "parent_content_id": "<parent_content_id>",
  "partition_day": "2026-08-27",
  "publish_location": "日本 日本海側",
  "publish_time": "2018-08-28T08:58:51",
  "quote_count": "1",
  "retweet_num": "1",
  "retweeted_content_id": "<retweeted_content_id>",
  "tag_checked_info": "1535417931000",
  "task_item": "1034243881263542272",
  "task_no_data": false,
  "video_urls": "https://pbs.twimg.com/ext_tw_video_thumb/1034243424356978694/pu/img/2crGII0nH74rMomk.jpg",
  "view_count": "<view_count>"
}

Integration

This App can be integrated via MCP, API, SDK, or file export. All channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API key (long-lived, created in the Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way. This App runs asynchronously and can be canceled midway: After you cancel, the run stops. Records already delivered are kept and billed.

With the MCP (Model Context Protocol), you can call this App directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.

Client config

Replace the value after Bearer with your long-lived API key. Works in any client, CI, or headless environment.

mcpServers config
{
  "mcpServers": {
    "octoparse_datahub": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=hello_moto/twitter-detail",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}

Let AI set it up for you

Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client. It will complete the setup its own way. (By default it guides you through signing in, and never asks you to send your API key in the chat.)

detail.access.mcp.composeHint

Pricing

Task start

Charged once per submitted run, regardless of how many records are returned.

$0.0001/ run
Returned detail record

Charged by the number of records successfully returned. Failed runs are not charged.

$0.0015/ record

Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.

View credits

Try it now

Fill in the parameters and run. Results come from a real call.

Example
Parameters are validated against input.schema before submission
From $0.0015 / record