Twitter Account List
Give a Twitter account ID and a maximum post count to get that account's public post list with content IDs and publish times
Source · en-USRevenir à la traduction
Aperçu
Want a working inventory of what a Twitter account posts, without scrolling the profile by hand? Give this App a public Twitter account ID and a maximum post count, and it returns that account's public posts as individual records. Each record carries the content ID, publish time, collection time, and the account identifier stored with the post, so research and monitoring teams can treat the timeline as a dataset rather than a webpage.
A profile page is built for reading one post at a time. This list is built for comparison: you can line up publish times, keep content IDs next to the account they came from, and see when each row was collected. The values are the public identifiers and timestamps captured with each post, not reconstructed from screenshots.
Data notes
The records come from a Twitter account's public post list and are ordered from newest to oldest by publish time. Each row is one public post, and the same content ID appears only once. Keyword and business ID repeat the account identifier stored on the post. Publish time, collection time, and clean update time are timestamps without an explicit timezone. Private, protected, deleted, or login-only posts are not included.
What a result looks like
Each record is one public post from the requested account:
| Content ID | Publish time | Keyword | Business ID | Collection time | Record ID |
|---|---|---|---|---|---|
| 2092517966604870070 | 2023-01-07T16:15:39 | 1611637588921815040 | 1611637588921815040 | 2026-08-26T17:24:16 | 6a8eb0c1a247355e51208cb2 |
| 2092518471989182858 | 2023-01-07T16:15:39 | 1611637588921815040 | 1611637588921815040 | 2026-08-26T17:24:16 | 6a8eb0c1a247355e51208cb0 |
Keyword type, source identifier, clean update time, and the no-data flag are also returned when present.
Example uses
- Build an account inventory by lining up Content ID, Publish time, and Keyword for the public posts you collected.
- Confirm you collected the intended account with Business ID before using Content ID in a report.
- Track freshness with Collection time next to Publish time to see when each post was captured.
Périmètre et limites
Each run processes 1 Twitter account ID. The requested post count is a strict maximum and the actual return will not exceed that value. Pull protection covers 1,000 result pages. Only publicly visible posts are covered.
- Adapté pour
- When you need a public post list for a specific Twitter account
- When you need content IDs, publish times, and collection timestamps for those posts
- À ne pas utiliser pour
- When you need private, protected, deleted, or login-only posts
- When you need tweet text, media, engagement counts, or profile details rather than post identifiers and timestamps
Gestion des échecs
Comportement en cas d'échec et de nouvelle tentative déclaré par l'auteur. Nous vous recommandons de l'inclure dans votre prompt système lors de l'intégration.
- 1If no data is returned, verify the Twitter account ID and confirm the account has publicly visible posts
- 2Retry later after rate limiting, temporary unavailability, or a timeout
- 3When the submission outcome is unknown, avoid immediate repeated submissions that could create duplicate tasks
- 4If authentication fails, verify the API Key configured for the execution environment
Entrée
Paramètres requis pour appeler cette App, générés à partir de l'input.schema du manifest.json.
| Champ | Nom métier | Type | Requis | Défaut | Énum / Contraintes | Exemple | Description |
|---|---|---|---|---|---|---|---|
| account_id | Twitter account ID | string | Oui | — | — | 1611637588921815040 | The Twitter account ID to collect, such as 1611637588921815040. Each run processes one account ID. Use 1 to 512 characters. |
| crawl_num | Maximum posts | integer | Oui | — | 1–2000 | 1 | The maximum number of public posts to collect for this account. The actual return will not exceed this value. Larger values take more time. |
Sortie
Structure des champs d'un enregistrement, générée à partir de l'output.schema du manifest.json.
| Champ | Nom métier | Type | Exemple | Description |
|---|---|---|---|---|
| biz_id | Business ID | string | 1611637588921815040 | Business identifier stored on the post record; it may be empty. |
| clean_update_time | Clean update time | string | 2026-08-26T17:24:17 | Timestamp when this record was last cleaned; it may be empty and has no explicit timezone. |
| content_id | Content ID | string | 2092517966604870070 | Public identifier of the Twitter post; it may be empty. |
| crawl_time | Collection time | string | 2026-08-26T17:24:16 | Timestamp when this post was collected; it may be empty and has no explicit timezone. |
| cur_id | Record ID | string | 6a8eb0c1a247355e51208cb2 | Identifier of this collected row; it may be empty. |
| keyword | Keyword | string | 1611637588921815040 | Account identifier stored on this post record; it may be empty. |
| keyword_type | Keyword type | string | account | Type label stored with the keyword, such as account; it may be empty. |
| no_data | No data | boolean | false | Whether this identifier produced no public posts. |
| publish_time | Publish time | string | 2023-01-07T16:15:39 | Timestamp when the post was published; it may be empty and has no explicit timezone. |
| source_item | Source identifier | string | 1611637588921815040 | Original account identifier associated with this record. |
Schema de l'enregistrement
La sortie est renvoyée enregistrement par enregistrement. detail.output.idFieldHint
{
"type": "object",
"properties": {
"biz_id": {
"type": "string",
"title": "Business ID",
"description": "Business identifier stored on the post record; it may be empty.",
"prefill": "1611637588921815040"
},
"clean_update_time": {
"type": "string",
"title": "Clean update time",
"description": "Timestamp when this record was last cleaned; it may be empty and has no explicit timezone.",
"prefill": "2026-08-26T17:24:17"
},
"content_id": {
"type": "string",
"title": "Content ID",
"description": "Public identifier of the Twitter post; it may be empty.",
"prefill": "2092517966604870070"
},
"crawl_time": {
"type": "string",
"title": "Collection time",
"description": "Timestamp when this post was collected; it may be empty and has no explicit timezone.",
"prefill": "2026-08-26T17:24:16"
},
"cur_id": {
"type": "string",
"title": "Record ID",
"description": "Identifier of this collected row; it may be empty.",
"prefill": "6a8eb0c1a247355e51208cb2"
},
"keyword": {
"type": "string",
"title": "Keyword",
"description": "Account identifier stored on this post record; it may be empty.",
"prefill": "1611637588921815040"
},
"keyword_type": {
"type": "string",
"title": "Keyword type",
"description": "Type label stored with the keyword, such as account; it may be empty.",
"prefill": "account"
},
"no_data": {
"type": "boolean",
"title": "No data",
"description": "Whether this identifier produced no public posts.",
"prefill": false
},
"publish_time": {
"type": "string",
"title": "Publish time",
"description": "Timestamp when the post was published; it may be empty and has no explicit timezone.",
"prefill": "2023-01-07T16:15:39"
},
"source_item": {
"type": "string",
"title": "Source identifier",
"description": "Original account identifier associated with this record.",
"prefill": "1611637588921815040"
}
},
"required": [],
"additionalProperties": false
}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.
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": {
"hello_moto__twitter-account-list": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=hello_moto/twitter-account-list",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}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
Facturé une fois par exécution soumise, quel que soit le nombre d'enregistrements renvoyés.
Facturé selon le nombre d'enregistrements renvoyés avec succès. Les exécutions échouées ne sont pas facturées. Facturé par unités de 20 enregistrement ; toute unité incomplète est arrondie à 20 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éditsData Apps associées
Ajoutez cette App et les recommandations ci-dessous à une même collection et générez une config MCP prête à brancher sur votre client IA.Regrouper ces Apps →
Details Twitter
Soumettez jusqu a 200 identifiants de publications Twitter et recuperez les details publics de publication, de compte, d engagement et de medias
hello_motoÀ partir de 0,0015 $US / enregistrementRecherche Twitter par mot-clé
Indiquez un mot-clé de recherche Twitter et un nombre attendu pour obtenir les identifiants de publications publiques correspondantes, leurs dates de publication et les métadonnées de collecte.
hello_motoÀ partir de 0,002 $US / 20 enregistrementTwitter Advanced Search Comments Scraper
Collect data from Twitter Advanced Search Comments Scraper.
YiJacobJohnRaku0,0006 $US / enregistrementEssayer maintenant
Renseignez les paramètres et lancez l'exécution — les résultats proviennent d'un appel réel.