Do I need official X API access or approval?

No. Your application uses an Openhandle API key. Openhandle handles the upstream integration behind redundant paths.

Will I need to resolve a handle to an ID first?

No. Use @username or the stable platform ID directly in any profile path, including /posts and /replies. Either form is one billed request.

All APIs

X (Twitter) API

Available

Get public X profiles, posts, replies, media, followers, lists, search, and more through the same API as Instagram and TikTok.

Get started for $0 Read the X docs

100 free requests, no card needed.

Endpoints

Everything public on X, 17 operations.

Profiles, posts, comments, and more, grouped by what they read. Each one is one call.

Profiles

6 operations

Get a profileGET /v1/twitter/profiles/{identifier}
List user postsGET /v1/twitter/profiles/{identifier}/posts
List user repliesGET /v1/twitter/profiles/{identifier}/replies
List user mediaGET /v1/twitter/profiles/{identifier}/media
List followersGET /v1/twitter/profiles/{identifier}/followers
List followingGET /v1/twitter/profiles/{identifier}/following

Posts

4 operations

Get a postGET /v1/twitter/posts/{identifier}
List post repliesGET /v1/twitter/posts/{identifier}/comments
List nested repliesGET /v1/twitter/posts/{identifier}/comments/{comment_id}/replies
List post repostersGET /v1/twitter/posts/{identifier}/reposters

Lists

3 operations

Get a listGET /v1/twitter/lists/{identifier}
List list membersGET /v1/twitter/lists/{identifier}/members
List list postsGET /v1/twitter/lists/{identifier}/posts

Search

4 operations

Search latest or top postsGET /v1/twitter/search/posts?q={query}&sort=latest
Search usersGET /v1/twitter/search/users?q={query}
Search images or videosGET /v1/twitter/search/media?q={query}&type=image
Search suggestionsGET /v1/twitter/search/suggestions?q={query}

Example

What an answer looks like.

A real X request and what came back. Every operation answers in this shape.

GET /v1/twitter/posts/1832277190… · 68ms

curl "https://api.openhandle.dev/v1/twitter/posts/1832277190…" \
  -H "Authorization: Bearer $OPENHANDLE_API_KEY"

200 OK · source cache

{
  "platform": "twitter",
  "resource": "post",
  "capturedAt": "2026-08-24T08:40:02Z",
  "source": "cache",
  "data": {
    "id": "1832277190…",
    "author": { "handle": "x", "isVerified": true, … },
    "media": [{ "type": "image", "url": "https://media.openhandle.dev/m_77qa1…" }],
    "metrics": {
      "views": 902114,
      "likes": 18233,
      "comments": 977,
      "shares": 4102,
      "saves": 1244,
      "reach": null
    }
    …more data
  }
}

Built for

Conversation monitoring
Audience research
News intelligence
Creator discovery

Known boundaries

X can change its public interfaces. Openhandle handles those changes behind the API.
Write actions and account login are not part of the public-data API.

FAQ

X questions.

Do I need official X API access or approval?: No. Your application uses an Openhandle API key. Openhandle handles the upstream integration behind redundant paths.
Will I need to resolve a handle to an ID first?: No. Use @username or the stable platform ID directly in any profile path, including /posts and /replies. Either form is one billed request.

Let your agent wire up X.

Copy one prompt. It has the docs, the spec, and an example request. Your agent reads it and builds against your test key.

Send your agent ahead.

Paste the prompt into your agent and it sets everything up. Or come yourself, it takes five minutes.

For agents

Get started for $0 Read the quickstart