Twitter/X Contact Intelligence: 200M+ Profiles Now in Signal API
Autobound Signal API now covers 200M+ Twitter/X profiles at the contact level. Query individual tweets, replies, and NLP-extracted pain points via the same enrichment endpoints.
TL;DR: Twitter/X contact-level intelligence expanded from ~4M to 200M+ profiles (50x). Every signal includes NLP-extracted pain points, initiatives, technologies, and sentiment. Query via /v1/contacts/enrich or /v1/signals/search. New content_filters param lets you filter by keyword. Bulk delivery available via GCS.
What Changed
We had Twitter/X signals before. But coverage was thin: roughly 4 million profiles, mostly executives and public figures. That's fine for enriching your top accounts, but useless for matching against a list of 500K contacts in a sales engagement platform.
As of this week, we cover 200M+ individual Twitter/X profiles at the contact level. Not company accounts. Individual people. Their posts, replies, engagement patterns, and the intelligence extracted from that content.
The math: if you're an OEM partner running contact match rates against our Twitter signal corpus, your hit rate just went up by roughly 50x. Contacts that previously returned zero social signals now have rich, recent Twitter activity attached.
What Is in a Twitter/X Signal
Raw tweets are noise. We do the extraction work so you don't have to. Every Twitter/X signal includes:
- Signal metadata: signal type (post, reply, engagement), timestamp, source URL, confidence score
- NLP-extracted pain points: What problems is this person talking about? Extracted and normalized.
- Initiatives mentioned: Projects, launches, migrations, evaluations referenced in their tweets
- Technologies mentioned: Tools, platforms, languages, frameworks they're discussing or using
- Sentiment: Positive, negative, neutral, with context on what the sentiment is directed toward
- Contact association: Linked to a specific person (name, title, company, email where available)
- Company association: Rolled up to the account level via our entity resolution layer
This is not a firehose of raw tweets. It's structured intelligence—same schema as every other signal type in the API—ready to feed an AI SDR, a scoring model, or a CRM workflow.
How to Query It
Contact Enrichment
The simplest path: pass a contact identifier and get back all signals, including Twitter/X activity.
curl -X POST https://signals.autobound.ai/v1/contacts/enrich \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"email": "jsmith@acmecorp.com",
"signal_types": ["twitter_post", "twitter_reply"]
}'Response (truncated):
{
"contact": {
"name": "Jane Smith",
"title": "VP of Revenue Operations",
"company": "Acme Corp",
"twitter_handle": "@jsmith_revops"
},
"signals": [
{
"signal_type": "twitter_post",
"timestamp": "2026-06-12T14:22:00Z",
"source_url": "https://x.com/jsmith_revops/status/1832...",
"content_snippet": "Just wrapped a 3-month eval of intent data providers...",
"extracted_intelligence": {
"pain_points": ["intent data accuracy", "vendor overpromising"],
"initiatives": ["intent data provider evaluation"],
"technologies_mentioned": ["Bombora", "6sense"],
"sentiment": "negative",
"sentiment_target": "incumbent intent data vendors"
},
"confidence": 0.92
}
]
}Signal Search with Content Filters
Need to find contacts tweeting about a specific topic? The new content_filters parameter lets you filter Twitter signals by keyword across your coverage universe.
curl -X POST https://signals.autobound.ai/v1/signals/search \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"signal_types": ["twitter_post", "twitter_reply"],
"content_filters": ["data infrastructure", "migrating off"],
"filters": {
"seniority": ["VP", "Director", "C-Suite"],
"employee_range": "201-1000"
},
"limit": 25
}'This returns contacts at mid-market companies whose recent Twitter activity mentions data infrastructure migration. The kind of signal that would take hours to find manually, delivered in milliseconds via API.
Use Cases for OEM Partners
If you're integrating Autobound signal data into your platform, here's what this unlocks:
1. AI SDR Personalization
Your AI SDR can now reference a prospect's actual recent tweets in outreach. Not generic "I saw you're active on Twitter" but specific: "You mentioned evaluating data infrastructure last week. Here's how [customer] approached the same problem." Match rates go from single digits to broad coverage across your contact database.
2. Social Listening at Contact Scale
Traditional social listening tools monitor brand mentions. This monitors individual contacts in your system. Upload 100K contacts, get back Twitter intelligence on every one that has a matched profile. No manual research, no per-seat social tool licensing.
3. Intent Signal Enrichment
A contact showing topic-level intent in your platform is interesting. That same contact publicly tweeting about evaluating vendors in that category is a confirmed buying signal. Layer Twitter signals on top of your existing intent data for higher-confidence scoring.
4. Competitive Displacement Triggers
Use content_filters to monitor contacts tweeting negatively about competitors. The NLP extraction does the sentiment work for you. Filter for negative sentiment + competitor name + decision-maker seniority = displacement opportunity list, updated continuously.
The Numbers
| Metric | Before | Now |
|---|---|---|
| Twitter/X profiles covered | ~4M | 200M+ |
| Coverage increase | – | ~50x (10,000%) |
| Signal granularity | Company accounts only | Individual contacts |
| Signal types | Posts | Posts, replies, engagement patterns |
| NLP extraction | Basic | Pain points, initiatives, technologies, sentiment |
| Keyword filtering | Not available | content_filters param (new) |
For bulk delivery customers: Twitter/X signals are available via GCS push on the same schedule as all other signal types. No additional configuration required if you're already receiving social signals.
What's Next
We're expanding the NLP layer to extract buying stage indicators from Twitter content (awareness vs. consideration vs. decision language patterns). And we're working on cross-platform signal correlation: when a contact tweets about a pain point AND posts about it on LinkedIn AND their company is hiring for the relevant role, that composite signal will surface automatically.
Resources
- API Reference: /v1/signals/search
- Full Signal Catalog (all signal types including Twitter/X)
- API Explorer (try it live, no setup)
- June 2026 What's New (content_filters, self-serve billing, more)
- Social Monitoring APIs for B2B Sales (full comparison guide)
Questions or need help with integration? Reach out directly or contact us here.