Brand and issue monitoring
Track public conversation surfaces and search results for campaigns, risks, or market signals.
Power monitoring, enrichment, and research workflows with X/Twitter API methods for profiles, posts, search, followers, social context, and feed-oriented data.
ScrapeStorm is not affiliated with X Corp. Make sure your usage respects applicable data rights, privacy rules, and platform terms.
X/Twitter teams usually start with public conversation monitoring, profile context, and post-level analysis. These workflows map commercial intents to practical API entry points.
Track public conversation surfaces and search results for campaigns, risks, or market signals.
Resolve public profile details and social context for CRM, research, and identity workflows.
Collect post details, feeds, and engagement-oriented signals for analytics.
Feed search and timeline-style data into alerting systems for public issues, campaigns, and market events.
Combine profile and social API methods to add public context to CRM, research, or creator datasets.
Browse every supported X/Twitter entity below, understand what each surface is for, and open the exact docs that matches your workflow.
Profile API methods resolve public identity, account context, and the base layer for creator, brand, or people-oriented products.
What you get. Use this entity to fetch account details, contacts, summary context, and the identifiers you need before moving into content or social API methods.
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Open these docs for a fast public snapshot of profile data before expanding into deeper monitoring or enrichment flows.
Use this API method for discovery work around profile when you need to find relevant public accounts, topics, or content quickly.
Use this API method to inspect the public conversation around profile and understand how people are reacting to the content.
Use these docs to work with profile: Posts by user ID when your product needs a clear API method into public profile workflows.
Choose this API method when your product needs a compact performance view around profile without opening a larger content collection.
Choose this API method when your product needs a compact performance view around profile without opening a larger content collection.
Search API methods expose public discovery surfaces, queries, and intent signals across the platform.
What you get. This entity is a natural entry point for research, prospecting, alerting, and products that need to find people, content, or topics fast.
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Choose this API method for geography-led workflows that begin with public place context and move into nearby content or local discovery.
Use this API method for discovery work around search when you need to find relevant public accounts, topics, or content quickly.
Use this API method for discovery work around search when you need to find relevant public accounts, topics, or content quickly.
Social API methods highlight public network relationships and the audience graph around supported profiles.
What you get. Use this group to understand followers, following, adjacency, and account relationships before you build scoring or campaign workflows.
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Start with these docs when you need relationship signals around social for audience research, scoring, or adjacency mapping.
Use this API method when you need compact follower ID lists for graph expansion, pagination, or downstream hydration.
Start with these docs when you need relationship signals around social for audience research, scoring, or adjacency mapping.
Use this API method when you need compact following ID lists for graph expansion, pagination, or downstream hydration.
Post API methods collect public publishing activity and the objects most teams use first for monitoring and analysis.
What you get. This group is a strong fit for feed views, archive jobs, campaign reporting, and any workflow that starts from the content stream itself.
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Use this API method to inspect the public conversation around posts and understand how people are reacting to the content.
Start here when you need richer public context behind posts: Details by post ID and want the most complete identity view first.
Use X/Twitter API methods as a layered workflow: profile context first, then posts, feeds, search, and social signals.
Start from public profile API methods so downstream post and social data can be tied to stable identities.
Use post and feed API methods for monitoring, reporting, and later classification.
Add search API methods when your product needs topic, brand, or issue discovery.
Use per-method prices to separate frequent lookups from richer social calls.
Start with one API method and use the docs link to inspect the exact request parameters and response structure.
usernamestrcurl --request GET \
--url "https://www.scrapestorm.net/api/v2/twitter.com/profile/info-by-username" \
--header "X-API-Key: 00000000-0000-4000-8000-000000000000" \
--get --data-urlencode 'username=value'
X-API-Key
username
API method pricing depends on the data surface and is visible in the shared pricing table.
ScrapeStorm is not affiliated with X Corp. Make sure your usage respects applicable data rights, privacy rules, and platform terms.
API method prices are visible before integration and credits are tied to successful API responses.
Each platform page links to the API reference and implementation docs for exact request and response details.
ScrapeStorm is independent from the listed platforms; your team remains responsible for permitted data processing.
These answers cover coverage, pricing, response formats, and launch details before you commit engineering time.
Where both versions exist, the same documentation page lets you switch between V2 normalized responses and V1 source-shaped responses.
No. ScrapeStorm is an independent data API and does not claim official platform partnership.
Yes. Search, post, feed, and profile API methods are structured for brand, issue, and conversation monitoring workflows.
Use profile API methods for account context and post API methods for content-level analysis, then combine them when your workflow needs both.
Use the pricing link on this page to review per-method credit costs before scheduling recurring jobs.