Skip to content
WebScrap

Twitter Scraping API for Public Posts and Profiles

Public posts, public profiles and public search results, returned as typed JSON from one call, with the rendering, the rotation and the retries already handled.
See pricing

Run a real request

Render
Extract
Status
...
Elapsed
... ms
Exit country
...
Browser used
...

This console sends a real request and shows you the real response. Five live fetches per session, and the sample targets run as often as you like.

What one call returns

TargetFields you get back
Posttext, author handle, posted at, reply, repost and like counts, media URLs, links, language
Profiledisplay name, handle, biography, joined date, follower and following counts, verified flag, avatar URL
Search or hashtaga list of posts with the same post fields, paginated
Threadthe ordered set of posts with author and position in the thread

Everything here is what an unauthenticated visitor can open in a browser. Nothing behind a login, a protected account or a paid tier is available through this endpoint, and no credentials of yours are ever forwarded.

The page is an empty shell without a browser

The timeline is assembled by scripts after the document arrives, so a raw fetch returns markup with no posts in it. Browser rendering, a wait for the content selector and a consistent browser identity are what turn that into data, and all three are parameters of the same request. The mechanics are on the web data scraping page.

What teams collect this for

  • Brand and reputation monitoring: what is being said about a name, in which language, at what volume.
  • Market and sentiment research, where the daily change matters more than any single post.
  • Campaign measurement, tracking the spread of a hashtag or a link over days rather than minutes.
  • Public figure and competitor tracking for media and analyst teams.

Scheduled jobs on Growth and above run the same query set on a schedule and post each run to your endpoint.

What you should check before you collect

Posts and profiles are written by people, so the data is personal data even when it is public. GDPR and similar laws follow it into your database: you need a basis for keeping it, a retention period and an answer when someone asks what you hold. The platform terms you accepted, if you accepted any, can bind you further. We wrote the longer discussion in is web scraping legal, and it is not legal advice.