X (Twitter) Email Lookup & Profile Finder

Find email associations for X / Twitter usernames, or reverse-search an email address to discover matching public X profiles. The Actor combines association matching with a current X profile check, so saved profile results contain up-to-date public account details instead of an unverified username alone.

Enter usernames, email addresses, or both. No X login, cookies, API key, or proxy configuration is required. Results can be exported as JSON, CSV, Excel, XML, or RSS and used through the Apify API, schedules, webhooks, and integrations.

What can this X email lookup do?

• Find email addresses associated with an X username, @handle, or profile URL.
• Reverse-search an email address for associated X accounts.
• Confirm that a matched X account is currently available before saving its profile.
• Return public profile data such as the display name, bio, location, follower counts, verification status, profile image, and account creation date.
• Normalize and deduplicate equivalent usernames and case-insensitive email addresses.
• Process up to 100 valid, unique usernames and email addresses in one run.
• Save clear status rows when an input has no match or its associated X account is unavailable.

How to use

1. Add one or more values under X usernames or Email addresses.
2. You may fill in either section or use both in the same run.
3. Select Start.
4. Open the Dataset Overview to review matched profiles.
5. Open Status rows to understand inputs that did not produce an available profile.
6. Export the Dataset or connect the Actor to an API, schedule, webhook, Make, Zapier, Google Sheets, or another Apify integration.

Input

Field	What to enter
usernames	X usernames such as apify, handles such as @apify, or profile URLs such as https://x.com/apify
emails	Complete email addresses. Matching is case-insensitive, so Name@Example.com and name@example.com are treated as the same input

The combined limit is 100 valid, unique values per run. Blank or malformed values are ignored. Equivalent usernames and repeated email addresses are queried only once. If the normalized batch exceeds the limit, the Actor returns a friendly invalid_input status row instead of silently truncating the request.

{
  "usernames": [
    "apify",
    "https://x.com/example_account"
  ],
  "emails": [
    "contact@example.com"
  ]
}

Output

Each successful Dataset item represents one unique, currently available X account. The associated email addresses are grouped with the current public profile data.

The following JSON is an illustrative structure. Actual values are returned only when an association exists and the X profile is available.

{
  "status": "success",
  "user_id": "123456789",
  "screen_name": "example_account",
  "name": "Example Account",
  "emails": [
    "contact@example.com"
  ],
  "profile_url": "https://x.com/example_account",
  "description": "Example public profile bio",
  "location": "San Francisco",
  "created_at": "2020-01-15T10:30:00Z",
  "website_url": "https://example.com",
  "profile_image_url": "https://pbs.twimg.com/profile_images/example_normal.jpg",
  "followers_count": 12500,
  "following_count": 420,
  "tweets_count": 3100,
  "verified": false,
  "is_blue_verified": true,
  "protected": false
}

Depending on what X returns for an account, results can also contain profile banner, media count, likes given, list count, verification type, professional categories, creator subscriptions, sensitivity status, and account labels.

Status rows

Inputs without a saved profile remain visible as lightweight diagnostic records:

Status	Meaning
not_found	No association was found for the supplied username or email address
account_unavailable	An association exists, but the X account is unavailable, suspended, or no longer exists
lookup_failed	The association or current profile could not be checked; retry the input later
invalid_input	No valid input was supplied or the 100-input limit was exceeded

Status rows do not contain fabricated profile details.

Pricing

The Actor uses pay-per-event pricing. One email-profile-result event is charged for each unique, currently available X profile saved with at least one email association. Diagnostic rows such as not_found, account_unavailable, lookup_failed, and invalid_input are not charged as successful results.

Apify plan	Per successful profile	Per 1,000 successful profiles
Free	$0.0035	$3.50
Bronze	$0.0030	$3.00
Silver	$0.0027	$2.70
Gold	$0.0025	$2.50
Platinum	$0.0025	$2.50
Diamond	$0.0025	$2.50

An apify-actor-start event costs $0.00005 per run. Platform usage is included in the configured event prices. Use Maximum cost per run in Apify Run options when you need a fixed spending limit. The Pricing tab is the source of truth if prices change later.

API example

curl -X POST \
  "https://api.apify.com/v2/acts/arjun_code~x-twitter-email-lookup/runs" \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"usernames":["apify"]}'

The run's output links to the default Dataset, where results can be downloaded in multiple formats.

Data coverage, privacy, and responsible use

An email association means that the address and X username are linked in the available association data. It does not prove that the mailbox is currently deliverable, that the account owner still controls it, or that the owner has publicly disclosed it. Association data can be incomplete, historical, or outdated. Public X profile fields are refreshed only after a match is found.

Lookup inputs are transmitted over HTTPS to a creator-operated matching service so the requested association can be checked. Only submit personal data that you are authorized and legally permitted to process. Do not use the Actor for spam, harassment, impersonation, unlawful surveillance, or other activity that violates applicable law, X's terms, or Apify's Acceptable Use Policy.

For a correction, removal request, or support question, open an issue on the Actor page and identify the affected association without posting additional sensitive information publicly.

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by X Corp.

FAQ

Why did my input return not_found?

The available association data did not contain a match. This does not prove that no email address or X account exists.

Why was a matched account not saved?

The associated X account may be suspended, deleted, renamed, temporarily unavailable, or inaccessible during the current check. Review the Status rows view for the exact outcome.

Are the returned emails verified?

No. They are association records, not live mailbox-verification results. Verify suitability, accuracy, and permission before using them.

Can I automate recurring lookups?

Yes. Save the input as an Apify Task, run it on a schedule, or connect the Dataset to webhooks and integrations.