X extraction / 2026

How to scrape data from X in 2026

A public X status URL can be useful evidence for an AI workflow, but the surrounding interface is not. A post entity keeps the text, author, date when available, and original link in a reusable representation.

Quick answer

Use the public page URL you already have.

Send the ordinary public X URL to extractor.sh. Choose JSON for stable fields or Markdown when an AI model will read the result directly. The API uses GET, so an identical successful request can be served from Cloudflare’s edge cache.

curl --get 'https://extractor.sh/api/extract' \
  --data-urlencode 'url=https://x.com/jack/status/20' \
  --data-urlencode 'format=json'

Available data

What you can extract

Public post text
Public author information
Canonical status links
Publication timestamps when available

AI workflows

Where normalized data helps

AI research with source links
Public announcement monitoring
Knowledge-base ingestion
Cross-platform content normalization

AI-ready output

Markdown for models. JSON for systems.

Raw HTML consumes tokens on navigation, scripts, styling, and interface labels. Clean Markdown keeps the readable hierarchy for LLM prompts and RAG chunks. Normalized JSON is better when your application needs an explicit semantic type, source, author, publication date, media, attributes, and collection items.

Always retain the canonical URL from the response. AI-generated summaries should remain traceable to the public source, especially when the underlying page can change.

Boundaries

Public data only

Only individual public status URLs are supported.
Private, deleted, and age-gated posts are unavailable.
Timelines, search results, replies, and complete threads are not included.

extractor.sh does not bypass CAPTCHAs, login walls, paywalls, access controls, or regional restrictions. Review the source’s terms and applicable law before collecting or reusing data.