ES

Twitter Account Info

Collect public profile details, audience metrics, and verification signals for one or more Twitter accounts

Original · en-USVolver a la traducción

Desarrollador
Precios
Desde 0,0015 US$ / registro
Última actualización
2026-09-18

Descripción general

Twitter and X profile pages mix identity, audience size, verification, and protection signals in a layout that is hard to compare across accounts. This app turns those public profiles into a consistent record set so research, partnership, and monitoring teams can work from the same identifiers, metrics, and timestamps.

The value is the joined profile snapshot: displayed name, username, account ID, public URL, follower and following figures, verification and protection flags, bio text, and collection time stay together for each submitted username. That makes it easier to qualify creators, compare audience scale, and keep a watch list current without reconstructing profiles by hand.

Data notes

The data comes from the public Twitter profile associated with each submitted username. One record is produced for each submitted username when the source returns a profile or a no-data marker. Duplicate submitted usernames are removed across collected pages. Audience counts, bio text, professional attributes, location, and timestamps retain the source text; a source value can be unavailable and appear empty. Follower count, Following count, Fast followers, Like count, Listed count, Media count, and Post count are kept as source text rather than normalized numbers. Can DM, Media tag, Protected account, Translator, Custom timelines, Graduated access, and Sensitive are also retained as source text, even when they look like yes/no flags. Has email, Verified, and YouTube linked are true/false values. Collected at and Joined at are preserved as supplied, without inferring a timezone. Private, suspended, and login-only accounts are outside the coverage.

What the results look like

Each record represents the public profile collected for one submitted Twitter username.

Account nameUsernameFollower countVerifiedSubmitted accountNo data
💫Etoiles💫000uTSIDER2No000uTSIDERNo
demo.accountYes

Additional values include Avatar URL, Profile URL, Account ID, Bio, Affiliate label, Business ID, Can DM, Media tag, Cover photo URL, Collected at, Entity type, Fast followers, Following count, Custom timelines, Graduated access, Profile entities, Has email, Protected account, Translator, YouTube linked, Joined at, Source keyword, Like count, Listed count, Location, Media count, Pinned tweets, Sensitive, Professional info, Interstitial type, Post count, and Translator type.

Use cases

  • Qualify partnership targets by comparing Account name, Username, and Follower count across a watch list.
  • Map public presence by lining up Profile URL, Bio, Location, and Joined at for accounts you already monitor.
  • Separate empty outcomes from usable profiles by checking No data together with Submitted account before using Like count or Post count.
  • Distinguish public versus restricted profiles by reading Protected account, Verified, and Sensitive together with Account name.

Alcance y límites

Each run accepts 1 to 200 Twitter usernames and returns at most one public profile record per username when data is available.

  • Adecuada para
  • When you need a current public profile snapshot for specific Twitter accounts
  • When you need displayed audience size, verification, protection, and public profile signals in one record
  • No usar para
  • When you need posts, comments, or search results rather than account-level profile information
  • When you do not have a Twitter username to collect

Gestión de fallos

Comportamiento de fallos y reintentos declarado por el desarrollador. Recomendamos incluirlo en tu prompt del sistema al integrar.

  1. 1If no profile data is returned, verify the username and confirm the account is still public
  2. 2Retry later after rate limiting, temporary unavailability, or a timeout
  3. 3When the submission outcome is unknown, avoid immediate repeated submissions that could create duplicate tasks
  4. 4If authentication fails, verify the API Key configured for the execution environment

Entrada

Parámetros necesarios para llamar a esta App, generados a partir del input.schema del manifest.json.

  • Twitter username listitemsObligatorioarray<object>
    The Twitter usernames to collect. Submit 1 to 200 items; each item needs one username.
    Cantidadhasta 200 elementosEjemplo[{"account":"000uTSIDER"}]

Salida

Estructura de campos de un único registro, generada a partir del output.schema del manifest.json.

  • Submitted accounttask_itemstring
    The username submitted for this record
    Ejemplo000uTSIDER
  • No datano_databoolean
    Whether this submitted username returned no public profile
    Ejemplofalse
  • Source keywordkeywordstring
    The source keyword associated with the collected account
    Ejemplo000uTSIDER
  • Account IDaccount_idstring
    The Twitter account identifier returned for the profile
    Ejemplo1652063959627841537

Datos de ejemplo

Generado a partir de output.schema. Los campos sin valor de ejemplo usan marcadores de estructura.

output.example
{
  "task_item": "000uTSIDER",
  "no_data": false,
  "keyword": "000uTSIDER",
  "account_id": "1652063959627841537",
  "account_name": "💫Etoiles💫",
  "account_avatar_url": "https://pbs.twimg.com/profile_images/1718476282885808128/3IcN2Gim_normal.jpg",
  "account_home_url": "https://x.com/000uTSIDER",
  "account_signature": "she/her",
  "affiliates_highlighted_label": "{\"label\":null}",
  "biz_id": "000uTSIDER",
  "can_dm": "false",
  "can_media_tag": "true",
  "cover_photo_url": "<cover_photo_url>",
  "crawl_time": "2026-08-27T14:07:55",
  "entity_type": "user",
  "fans_count": "2",
  "fast_followers_count": "0",
  "friends_count": "17",
  "has_custom_timelines": "false",
  "has_graduated_access": "true",
  "info": "{\"description\":{\"hashtags\":null,\"urls\":null,\"userMentions\":null},\"url\":null}",
  "is_mail": false,
  "is_protected": "false",
  "is_translator": "false",
  "is_verified": false,
  "is_youtube": false,
  "joined_date": "2023-04-29T05:35:28",
  "likes_count": "7093",
  "listed_count": "0",
  "location": "<location>",
  "media_count": "5",
  "pinned_tweet_ids": "<pinned_tweet_ids>",
  "possibly_sensitive": "false",
  "professional": "<professional>",
  "profile_interstitial_type": "<profile_interstitial_type>",
  "publish_content_count": "202",
  "translator_type_enum": "none",
  "user_handle": "000uTSIDER"
}

Integración

Esta App se puede integrar mediante MCP, API, SDK o exportación de archivos — todos los canales comparten las mismas capacidades y precios. Cada solicitud se autentica con la cabecera Authorization: Bearer usando una API Key (de larga duración, creada en la consola de Data Hub); los clientes MCP también pueden iniciar sesión con OAuth sin clave. Más opciones como CLI y Skill están en camino. Esta App se ejecuta de forma asíncrona y se puede cancelar a mitad de camino: Tras la cancelación, la ejecución se detiene. Los registros ya entregados se conservan y se facturan.

Con MCP (Model Context Protocol) puedes llamar a esta App directamente desde clientes de IA como Claude y Cursor. Elige tu cliente y el modo de autenticación, y copia la configuración de abajo.

Configuración del cliente

Sustituye el valor tras Bearer por tu API Key de larga duración. Funciona en cualquier cliente, CI o entorno sin interfaz.

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

Deja que la IA lo configure por ti

¿No quieres editar configuraciones a mano? Copia el prompt de instalación y pégalo en cualquier cliente de IA: completará la configuración a su manera. (De forma predeterminada te guía para iniciar sesión y nunca te pide que envíes tu API Key en el chat.)

detail.access.mcp.composeHint

Precios

Task start

Se cobra una vez por cada ejecución enviada, independientemente del número de registros devueltos.

0,0001 US$/ ejecución
Returned profile

Se cobra según el número de registros devueltos correctamente. Las ejecuciones fallidas no se cobran.

0,0015 US$/ registro

Los distintos eventos de facturación se acumulan de forma independiente. Consulta cada elemento para más detalles. Las ejecuciones fallidas no se cobran.

Ver créditos

Pruébalo ahora

Rellena los parámetros y ejecuta — los resultados provienen de una llamada real.

Ejemplo
Los parámetros se validan contra input.schema antes del envío
Desde 0,0015 US$ / registro