The X API for products and pipelines.

Retrieve supported public X data — profiles, post feeds, single posts, the Highlights tab, and Communities — through REST endpoints that return one consistent response model.

Get free API key View the docs

7 supported endpoints
Public data only
Fetched at request time

GET/v1/x/posts/{postId}200OK

{
  "type": "Note",
  "content": "The sky is full of excitement this month! You…",
  "published": "2026-07-31T20:57:39.000Z",
  "viewCount": 1991209,
  "likeCount": 5333,
  "repostCount": 1212,
  "replyCount": 162,
  "quoteCount": 67,
  "attributedTo": {
    "preferredUsername": "NASA",
    "followerCount": 92244633
  }
}

What you can pull from X.

On X you get what the platform serves a logged-out visitor, and nothing past it. A profile returns bio, follower counts, verification flags, and images. A single post returns its text, author, engagement counts, and media. Communities are covered as their own object with a timeline and a media tab.

The feed endpoints need one piece of care that the other platforms do not. They return a ranked public selection rather than a strict reverse-chronological timeline, and consecutive pages can overlap — a pinned post reappears on every page. Deduplicate by id when paging, and do not treat feed position as publication order.

Every response uses the same ActivityStreams 2.0-based model as the other supported platforms, so a X integration reuses the parsing you already wrote. Fields specific to X stay as documented first-class fields rather than being flattened away.

X data

Public profiles with follower counts and flags
User post feeds and the Highlights tab
Single posts with engagement and media
Community metadata
Community timelines and media tabs

All 7 X endpoints.

Grouped by what they return. Every one has its parameter contract, a request you can copy, and an example response.

Profiles

The two records an X run can be anchored to: an account, and a community.

Get user profileReturns profile information for a public X account including bio, follower counts, verification flags, and profile images.GET /v1/x/users/{username}Get communityReturns public metadata for an X community, including description, member count, topic, creator, and banner image.GET /v1/x/communities/{communityId}

Feeds

An account’s timeline and Highlights tab, and a community’s posts and media tab — four cursor-paginated reads.

Get user postsX API: Returns public posts from a user's profile as visible to not logged in users. This feed is not guaranteed to be chronological and is often a ranked…GET /v1/x/users/{username}/posts Get user highlightsX API: Returns the public Highlights tab selection as visible to not logged in users. This feed is not guaranteed to be chronological. Pages may overlap: a…GET /v1/x/users/{username}/highlights Get community postsFetch public posts from an X community timeline as visible to logged-out users for community research.GET /v1/x/communities/{communityId}/posts Get community mediaFetch public posts from an X community Media tab as visible to logged-out users for community media research and monitoring.GET /v1/x/communities/{communityId}/media

Posts

One post by id, carrying the same engagement counts and media the feeds already return.

Get postFetch a public X post with its text, author, engagement counts, and media attachments for content analysis and competitive research.GET /v1/x/posts/{postId}

How the calls fit together.

Few X jobs are a single request. Most are two or three chained, each call keyed by an id the one before it returned.

Track an account

Read the profile for the baseline, page the public timeline, then the Highlights tab for what the account pinned as its best.

Read a community

Take the community for its size and topic, then its timeline and media tab for what it is actually posting.

What shapes your X integration.

Page sizes, ordering, and what the platform itself withholds — the details that decide how you build, settled before you write a line of code.

01Feeds are ranked, not chronological: The user post feed and the Highlights tab return the public selection a logged-out visitor sees. It is not guaranteed to be in publication order, so sort by the published timestamp yourself if order matters.
02Pages overlap — deduplicate by id: A pinned post is repeated on every page of a feed. Paging without deduplicating by id will double-count it.
03Logged-out visibility is the boundary: Every X endpoint returns what the platform serves without an account. Anything gated behind a login is out of scope and is not available through a different call.
04Communities are addressed by id: Community metadata, its timeline, and its media tab are three endpoints keyed by the numeric community id from the community URL.

Read the X reference Make your first request

Other platforms

Build on X data.

Get a free API key and call any of these endpoints in minutes. No credit card required.

Get free API key X reference