logoPandorLabs
Real time, in public

X (Twitter) Data, Delivered

Public X (Twitter) content and engagement metrics, normalised to the same schema as every other platform we cover and pushed into your stack. Nothing to build, nothing to maintain.

source specification

Source
x.com
Objects
Posts and replies, Public profiles, Quote posts and reposts, Search and keyword feeds, Engagement metrics
Formats
JSON · CSV · Parquet
Refresh
Continuous to daily
Scope
Public content only

about the platform

What makes X (Twitter) different

X remains the platform where things are said first. News breaks here, executives make announcements here before the press release lands, and complaints reach a company here faster than through any support channel — which is why the platform’s value is almost entirely a function of latency. Its structure is conversational and public by default: replies, quote posts, and reposts form threads that can be reconstructed in full, and the quote post in particular is a uniquely legible signal, because it carries an explicit opinion attached to the thing being shared. Cashtags give financial discussion its own addressable namespace, which no other network offers.

why teams track it

Why X (Twitter) data is worth having

If your use case has any time sensitivity — market-moving news, crisis detection, live event tracking, or breaking product issues — this is the source where the clock starts. Trading and research teams use cashtag and keyword streams as an event feed, comms teams use it as the earliest possible warning that a story is forming, and support teams use public complaint volume as a leading indicator of an incident.

Visit x.com

applications

What teams build on X (Twitter) data

Breaking news and market event detection

Keyword and cashtag streams delivered as webhooks the moment a match is detected. For anything trading-adjacent, the difference between sub-minute and hourly delivery is the difference between a signal and a post-mortem.

Crisis detection and comms early warning

A sudden change in mention volume against your brand terms is the earliest warning a story is forming. Detecting it in minutes rather than at the next morning’s report changes what response is still available to you.

Quote-post opinion mining

A quote post is a share with an argument attached, which makes it far more informative than a plain repost. It shows not just what is spreading but which framing is spreading with it.

Executive and competitor monitoring

Company accounts and named executives tracked continuously, so a strategy shift signalled in a post reaches your team the same day rather than via a newsletter a week later.

Live event and campaign tracking

Volume, sentiment, and reach against an event hashtag as it happens, which is when the numbers can still inform what you do next.

Conversational AI training data

Threaded reply chains with clear parent-child structure and a public engagement signal, in short-form conversational register that is hard to source elsewhere.

what you get back

Fields in the X (Twitter) feed

Platform-specific detail on top of the unified social schema, so a dashboard built on one platform works on the next without a rewrite.

  • Post text, hashtags, cashtags, mentions, and attached links
  • Reply, repost, quote, like, and view counts where exposed
  • Conversation threading — parent post, reply chain, and quote relationships
  • Public profile attributes — handle, display name, bio, follower counts, verification state
  • Posting timestamp at second resolution
  • Language and attached media type

Public surfaces only

We collect what a logged-out visitor can see. No authentication is bypassed, no private content is touched, and no attempt is made to deanonymise anyone.

One schema across platforms

A post from any network arrives with the same field names, so adding a platform does not mean rewriting anything downstream.

Deletion propagates

When content is removed at source it drops out of subsequent deliveries, and retention windows on delivered data are configurable per engagement.

10+
Platforms covered
<60s
Detection latency
3
Delivery formats
99.9%
Uptime SLA

questions

Frequently Asked Questions

Everything you need to know before you send us your first request.

Detection latency on tracked terms and handles is under a minute, and matches are pushed to your webhook endpoints as they are found rather than batched. For time-sensitive work this is the whole point of the source, so it is the parameter we scope first.
Yes. Parent-child relationships across replies, and the link between a quote post and the post it quotes, are preserved rather than flattened. A reply read without its parent is frequently meaningless — disagreement, correction, and sarcasm all depend on what came before it.
Yes, and it is one of the more common configurations on this source. Cashtags give financial discussion an addressable namespace that no other platform provides, and they can be combined with keyword and account tracking in the same feed.
Not for the data. The objects, fields, and threading model we deliver are unchanged, and the schema is stable across the rename. We use x.com as the canonical domain and keep the Twitter naming in our own documentation where it still helps people find things.
Into the systems you already run. Normalised records land as JSON, CSV, or Parquet in S3, GCS, or Azure Blob, or straight into Snowflake or BigQuery, on whatever cadence you set. Webhooks push matches to your endpoints as they are detected, which is how most customers wire alerting. A solutions engineer sets the schema, cadence, and destination with you during onboarding.
Keeping the collector working is our responsibility. Extractors are monitored continuously, and when the platform changes its structure we patch upstream while the schema we deliver to you stays fixed. If a change causes a coverage gap we tell you which window was affected rather than quietly returning fewer records.
Pricing is scoped per engagement — the number of tracked terms, handles, or communities, the refresh cadence, and the delivery destinations involved. Historical backfill is quoted separately. Every engagement starts with a free sample run against your own brand terms, so you can judge the data before committing.

Still have questions?

Talk to an engineer

Ready to Get Started?

Talk to us about your sources and volume. We'll return a sample dataset from your target sites before you commit to anything.

SOC 2 Type II
GDPR & CCPA compliant
99.9% uptime SLA

© 2026 PandorLabs, Inc. All rights reserved.