Published June 2026. Official X API figures reflect the April 20, 2026 pay-per-use update and were verified June 2026. The tactics here account for the retired Twitter Lead Generation Card and the recent move of follow, like, and quote endpoints to Enterprise-only access.
Contents
- What is a lead on Twitter/X?
- Are Twitter Lead Generation Cards still available?
- How to find leads on Twitter/X: the programmatic playbook
- How to qualify a lead before reaching out
- The data layer is not the contact layer
- What it costs: API access versus marketing tools
- Common mistakes in Twitter lead generation
- Getting started
- FAQ
Key takeaway: Finding leads on Twitter/X means identifying accounts whose public activity signals buying intent, then qualifying them by profile fit. The reliable method is programmatic: search bios for ideal-customer keywords, surface tweets that express a need, tap competitor follower lists, and monitor target-account Lists. Public data supports discovery and qualification, not contact details.
Sorsa API is an alternative Twitter/X API that turns that method into a handful of REST calls. Match prospects by bio with the search-users endpoint, surface buying-signal tweets with search-tweets, and pull up to 200 follower profiles per request with followers, all on flat per-request pricing that starts at $49 for 10,000 requests, with a flat 20 requests per second on every plan and no OAuth, no app review, and no approval queue. One honest limit stated up front: a read-only public-data API finds and qualifies prospects, it does not return private emails or send messages, so outreach stays in your own stack.
What is a lead on Twitter/X?
A lead on Twitter/X is a public account whose posts or profile show genuine interest in a product, service, or topic, and that matches a seller's target criteria such as role, industry, or company size. The strongest signals are tweets describing a need, repeated engagement in a relevant topic, and bio details that fit the ideal customer profile.
Two things separate a lead from a follower. The first is intent: a tweet asking for a tool recommendation, complaining about a current vendor, or naming a problem your product solves is a buying signal you can read directly. The second is fit: the bio, location, and the accounts a user follows tell you whether they sit inside your market at all.
This works in both directions. B2B sellers find decision-makers by role keywords and the topics they discuss, while consumer brands find prospects by interest and intent phrases. Either way, the raw material is public, which is what makes Twitter/X a practical channel for finding prospects at scale rather than one conversation at a time.
Are Twitter Lead Generation Cards still available?
No. Twitter retired the Lead Generation Card in 2017, removing the ability to create or edit the cards on February 1, 2017 and to display them on March 1, 2017, per the platform's Ads API deprecation notice. Lead capture on X now runs through standard ad formats, and organic prospecting relies on public search, profile data, and follower lists.
This matters because a large share of "Twitter lead generation" guides still present the card as a current tactic. It has been gone for years. The advertising path today is website cards and conversion campaigns inside the X Ads suite; the organic path is the search-and-qualify workflow below.
A second recent change affects automation-style tactics. As of the April 20, 2026 pricing update, the official X API moved follow, like, and quote-post endpoints to Enterprise-only access, so the old "auto-follow your prospect list" approach is no longer available on self-serve API tiers. Reading public data to find and qualify prospects remains fully available, and it is the part that scales cheaply.
How to find leads on Twitter/X: the programmatic playbook
Finding leads on Twitter/X programmatically follows five steps: define the ideal customer profile, match it against public bios and tweets, surface accounts showing buying intent, monitor relevant conversations, then qualify the shortlist before any outreach. Each step maps to a public-data search or profile lookup.
- Match prospects by ideal-customer keywords in their bios.
- Surface tweets that express a need or buying intent.
- Monitor brand and competitor mentions for warm leads.
- Tap existing audiences: competitor followers and curated Lists.
- Qualify on fit and recent activity, then hand off to outreach.
The sections below show each step against real endpoints. All calls use the base URL https://api.sorsa.io/v3 and a single ApiKey header.
Match prospects by bio keywords
The fastest first pass is bio search. People state their role, company, and niche in their bio, so a keyword query returns accounts that already describe themselves as your target. The search-users endpoint takes a query and returns full profiles, including follower count, location, bio, account age, and verification status.
curl -X POST https://api.sorsa.io/v3/search-users \
-H "ApiKey: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query": "founder devtools"}'
Each result is a complete profile, so you can filter the raw set down to a clean shortlist: micro accounts under a follower threshold, a single country, verified accounts only, or accounts created before a certain date. Pagination uses the next_cursor value returned with each page, so a few calls cover a deep result set. This is the same machinery behind broader target audience work, pointed at sales-ready accounts.
Surface buying-intent tweets
Bio search finds the right people; tweet search finds the right moment. Searching recent posts for phrases that signal a need surfaces prospects who are actively in-market, not just demographically a fit. The search-tweets endpoint accepts a query with Twitter advanced search syntax and an order of latest or popular.
curl -X POST https://api.sorsa.io/v3/search-tweets \
-H "ApiKey: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query": "need a CRM recommendation", "order": "latest"}'
The query is where intent lives. A short library of patterns catches most high-intent posts:
| Intent pattern | Example query | What it surfaces |
|---|---|---|
| Asking for a recommendation | "recommend a CRM" OR "best CRM for" | Buyers in active evaluation |
| Frustrated with a current tool | "frustrated with" plus a category term | Prospects ready to switch |
| Naming a competitor as a problem | competitor handle plus "alternative" | Competitive displacement leads |
| Describing the job to be done | "looking for a tool to" plus a task | Top-of-funnel intent |
Wrapping a phrase in quotation marks forces an exact-phrase match, OR widens the net, and since: and until: bound a date range. Each returned tweet carries its own engagement metrics (likes, replies, reposts, quotes, views), so you can rank results by traction and drop dead posts. For the full operator set, the advanced search operators reference covers the syntax in depth, and you can prototype a query in the browser with the free search query builder.
Monitor brand and competitor mentions
Some of the warmest leads are people already talking about you or a competitor. The mentions endpoint returns tweets mentioning a handle and adds server-side filters the general search does not have: min_likes, min_replies, min_retweets, and a since_date / until_date range in YYYY-MM-DD format.
curl -X POST https://api.sorsa.io/v3/mentions \
-H "ApiKey: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query": "competitorhandle", "order": "latest", "min_likes": 5, "since_date": "2026-06-01"}'
Pointed at a competitor, this surfaces their unhappy users and the people publicly asking them questions. Pointed at your own handle, it catches inbound interest you might otherwise miss. Run on a schedule, the same query becomes a steady feed of warm leads; the mechanics of polling and alerting are covered in the guide to real-time monitoring.
Tap existing audiences: followers and Lists
A competitor's follower list is a pre-qualified audience: people who care enough about the category to follow a vendor in it. The followers endpoint returns up to 200 profiles per request, so even large audiences are a handful of calls rather than thousands.
curl "https://api.sorsa.io/v3/followers?username=competitorhandle" \
-H "ApiKey: YOUR_API_KEY"
From there, filter by bio and follower count to keep only accounts that fit, and enrich a shortlist with batch profile lookups (up to 100 profiles in one request). The same approach drives deeper competitor audience analysis, and the step-by-step mechanics of pulling an audience are in the guide to extracting a follower list.
Twitter Lists are the other underused source. A List is a curated feed of specific accounts, which makes it ideal for tracking a set of target companies or a niche community. The List members endpoint returns the accounts in a List, and List tweets returns their posts, so a single List of your top prospect companies becomes a continuous prospecting stream.
Qualify, then hand off to outreach
Discovery produces a long list; qualification makes it useful. Score each candidate on three axes you can read from public data: fit (does the bio match the ideal customer profile), recency (have they posted in the last few weeks), and credibility (do their posts earn real engagement, or is the account dormant or fake). Drop everything that fails, keep the handles that pass, and pass them to your outreach tool.
That handoff is deliberate, and the next section explains why.
How to qualify a lead before reaching out
Qualify a Twitter/X lead on three signals readable from public data: profile fit, recent activity, and genuine engagement. Profile fit comes from the bio, location, and followed accounts; recency comes from the date of the latest tweets; engagement comes from the likes, replies, and views a user's recent posts actually earn. An account that fits the profile, posts regularly, and gets real responses is worth outreach.
Engagement is the cheapest fraud check you have. An account with a large follower count but only a few likes per post is often inflated, and a profile with a default avatar, no posts, and a brand-new creation date rarely converts. You do not need a proprietary score for this: pull the recent tweets, read the metrics, and set your own thresholds. Batch profile lookups let you enrich up to 100 handles per request, which keeps qualification fast even on a large shortlist.
The data layer is not the contact layer
A public-data API surfaces and qualifies prospects from information accounts have made public. It does not provide private contact details such as email addresses or phone numbers, and it does not send messages. Outreach and contact enrichment belong in dedicated, consent-aware tools that the seller controls.
This separation is a feature, not a gap. Some tools promise to "find" a prospect's email by guessing it from a handle and name; those guesses carry deliverability risk and sit in a legal gray area. The cleaner architecture is to use accurate public data to decide who is worth contacting, then handle the actual contact in a tool built for compliant outreach. That is exactly how the Twitter lead generation workflow is built: the API supplies the discovery and qualification layer, and your CRM or email platform owns the conversation. The same read-only public data also powers adjacent work like social listening, where the goal is signal rather than contact.
What it costs: API access versus marketing tools
The cost of finding leads on Twitter/X depends on read volume and the billing model. The official X API bills per resource fetched, so every profile or post in a response is a separate charge, while flat per-request API access charges one unit per call regardless of how many records that call returns. For read-heavy prospecting, the per-request model is far cheaper.
The gap is easiest to see on a concrete workload. Reading 1,000 prospect profiles costs about $10 on the official API and about a cent on a flat-rate plan; reading 1,000 intent tweets costs about $5 versus about ten cents.
| Axis | Official X API (pay-per-use) | Sorsa API |
|---|---|---|
| Pricing model | Per resource fetched | Per request (flat) |
| 1,000 prospect profiles read | $10.00 (1,000 x $0.010 per user read) | About $0.01 (5 follower requests, Pro) |
| 1,000 intent tweets read | $5.00 (1,000 x $0.005 per post read) | About $0.10 (50 requests, Pro) |
| Author profile inside a tweet | Billed as a separate user read | Included free |
| Authentication | OAuth 2.0 plus Bearer token | Single API key header |
| Rate limit | Varies by endpoint, windowed | Flat 20 requests per second, all plans |
| Follow, like, quote actions | Enterprise-only since April 20, 2026 | None (read-only) |
Official X API rates are taken from its pay-per-use schedule as of the April 20, 2026 update; Sorsa rates are flat per-request, with plans from $49 per month for 10,000 requests. On a read-heavy prospecting workload the saving lands at roughly 30 to 50x across a typical mix, and far more on follower-list reads where one request returns up to 200 profiles. The honest trade is direction of access: if you need to post, send DMs, or run engagement actions, that is the official API's territory, and follow, like, and quote moved to Enterprise-only access in April 2026; for read-heavy discovery at a flat, predictable price, the per-request model wins. Current flat per-request pricing lists every tier.
In one composite drawn from teams we work with, a roughly 12-person B2B SaaS sales group rebuilt its Twitter prospecting on the API. They ran a small set of buying-intent queries against search-tweets on a daily schedule, mined the follower lists of three competitors, and enriched the shortlist with batch lookups. The data side of that pipeline ran on the Pro plan, and reading the profiles and tweets came in roughly 30 to 50x below the official API's per-resource cost for the same volume. Outreach stayed in their existing email and CRM stack, where it belongs.
Common mistakes in Twitter lead generation
A few patterns waste time or invite trouble:
- Automating follows and likes. Aggressive auto-follow tools risk account action, and on the official X API those write endpoints are Enterprise-only since April 2026. Read public data; act manually or through compliant tools.
- Buying followers or chasing vanity audiences. Follower count is not fit. A small list of in-market accounts beats a large list of dormant ones.
- Mass-identical DMs. Generic outreach gets ignored and reported. Reference the specific tweet that flagged the prospect.
- Relying on guessed email addresses. Guessed contacts hurt deliverability and compliance. Qualify on public data, enrich contacts in a tool built for it.
- Ignoring recency. A perfect-fit account that has not posted in a year is rarely a live lead. Filter on recent activity.
Getting started
You can prototype prospecting queries in the browser before writing any code: the visual query builder is free to use, though pulling live data requires a paid API key. When you are ready to build, the search and follower endpoints are documented in the API reference, and setup is a single key in a header with no OAuth and no approval queue, typically about three minutes from sign-up to the first call. Plans start at $49 per month for 10,000 requests, with a flat 20 requests per second on every tier.
FAQ
What is a lead on Twitter/X?
A lead on Twitter/X is a public account whose posts or profile signal interest in a product or topic and that fits a seller's target criteria such as role, industry, or company size. The clearest signals are tweets describing a need, repeated engagement in a relevant topic, and bio details matching the ideal customer profile.
Can you get a lead's email address from Twitter?
No. Twitter/X does not expose private email addresses, and public-data APIs return only what an account has made public: profile, bio, links, and engagement metrics. A read-only API such as Sorsa surfaces and qualifies prospects from that public data, while contact enrichment and outreach happen in separate, consent-aware tools you control.
Is it legal to find leads on Twitter?
Reading public tweets and profiles to identify prospects is generally permissible when you stay within the platform's Terms of Service and avoid unauthorized bulk scraping or resale. Outreach is regulated separately: marketing to people in the EU must satisfy GDPR, and email outreach in the United States must follow the CAN-SPAM Act, including a clear opt-out.
How do you find high-intent prospects on Twitter?
Search recent tweets for phrases that express a need, such as asking for a tool recommendation or naming a competitor as a problem. With the Sorsa search-tweets endpoint you run those queries using Twitter advanced search operators and sort by latest, then read the engagement metrics on each result to prioritize active, credible accounts.
Are Twitter Lead Generation Cards still available?
No. Twitter retired the Lead Generation Card in 2017, disabling card creation on February 1 and display on March 1 of that year, per its Ads API deprecation notice. Modern lead capture on X runs through standard ad formats, while organic prospecting relies on public search, profile data, and follower lists.
How much does it cost to find leads on Twitter via API?
Costs depend on read volume. On a per-resource basis the official X API charges about $0.010 per profile read and $0.005 per post read as of its April 2026 pricing. Sorsa uses flat per-request pricing from $49 per month for 10,000 requests, and a single follower request returns up to 200 profiles, which makes read-heavy prospecting far cheaper.
Reviewed by Keksich, founder of Sorsa, marketer and X API researcher.
This guide draws on the Sorsa team's hands-on work operating the API, tested against the live v3 endpoints and the published API reference. Official X API pricing was taken from its current pay-per-use schedule as of the April 20, 2026 update; the retirement of the Lead Generation Card was confirmed against X's Ads API deprecation announcement. Compliance points reference the EU's GDPR and the US FTC's CAN-SPAM guidance. Verified June 2026.