X/Twitter Data API Featured API

X/Twitter Data API for profiles, posts, and social signals

Power monitoring, enrichment, and research workflows with X/Twitter API methods for profiles, posts, search, followers, social context, and feed-oriented data.

Profile enrichment Post monitoring Conversation search

ScrapeStorm is not affiliated with X Corp. Make sure your usage respects applicable data rights, privacy rules, and platform terms.

Use cases

What you can build

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.

01

Brand and issue monitoring

Track public conversation surfaces and search results for campaigns, risks, or market signals.

02

Profile enrichment

Resolve public profile details and social context for CRM, research, and identity workflows.

03

Post-level analysis

Collect post details, feeds, and engagement-oriented signals for analytics.

04

Issue and risk alerts

Feed search and timeline-style data into alerting systems for public issues, campaigns, and market events.

05

Audience context

Combine profile and social API methods to add public context to CRM, research, or creator datasets.

Entity directory

All supported entities

Browse every supported X/Twitter entity below, understand what each surface is for, and open the exact docs that matches your workflow.

X/Twitter profile data

6 API methods

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.

API methods inside this entity 6 API methods

Open the API method that matches the lookup, feed, summary, or discovery job you need.

X/Twitter social data

4 API methods

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.

API methods inside this entity 4 API methods

Open the API method that matches the lookup, feed, summary, or discovery job you need.

X/Twitter posts data

2 API methods

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.

API methods inside this entity 2 API methods

Open the API method that matches the lookup, feed, summary, or discovery job you need.

Launch path

How teams move from evaluation to launch

Use X/Twitter API methods as a layered workflow: profile context first, then posts, feeds, search, and social signals.

  1. 01

    Anchor by profile or handle

    Start from public profile API methods so downstream post and social data can be tied to stable identities.

  2. 02

    Collect post-level context

    Use post and feed API methods for monitoring, reporting, and later classification.

  3. 03

    Search public conversations

    Add search API methods when your product needs topic, brand, or issue discovery.

  4. 04

    Control operational cost

    Use per-method prices to separate frequent lookups from richer social calls.

Start here

First request

Start with one API method and use the docs link to inspect the exact request parameters and response structure.

API method Profile: Info by username
Request cost 2 credits

Required parameters

usernamestr
GET /api/v2/twitter.com/profile/info-by-username
curl --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'
Auth header X-API-Key
Required parameters username
Billing event 2 credits per successful response
Launch details

Pricing, monitoring, and launch details

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 methods15
Entities4
Credits2 credits

Per-success credit pricing

API method prices are visible before integration and credits are tied to successful API responses.

API reference and implementation docs

Each platform page links to the API reference and implementation docs for exact request and response details.

Responsible data use

ScrapeStorm is independent from the listed platforms; your team remains responsible for permitted data processing.

Details

Questions before launch

These answers cover coverage, pricing, response formats, and launch details before you commit engineering time.

Coverage 4 entities
Credits 2 credits
Health status Check API status
Do X/Twitter pages expose both V1 and V2 methods?

Where both versions exist, the same documentation page lets you switch between V2 normalized responses and V1 source-shaped responses.

Is this an official X/Twitter API?

No. ScrapeStorm is an independent data API and does not claim official platform partnership.

Can I use X/Twitter API methods for brand monitoring?

Yes. Search, post, feed, and profile API methods are structured for brand, issue, and conversation monitoring workflows.

How do I choose between profile and post endpoints?

Use profile API methods for account context and post API methods for content-level analysis, then combine them when your workflow needs both.

Where do I check API method pricing?

Use the pricing link on this page to review per-method credit costs before scheduling recurring jobs.