X (Twitter) posts API for AI assistants

List a user's recent posts. 7 endpoints from 6 providers, from $0.000495 per call.

Providers

Prices include the router's 10% markup and are paid from the usage wallet. Checked on November 11, 2026.

The X user posts API takes a Twitter handle and returns recent posts from that account's timeline, each with its text, when it was posted, and engagement counts. The reply is JSON, so your assistant reads the posts directly without opening a browser.

What it does

You pass the handle, such as levelsio or nasa, and the API returns the account's recent posts. Some providers let you set a page size or pass a cursor to get older posts, and some let you exclude replies or retweets.

Each post in the reply has the text, the post time, and counts for likes, retweets, and replies. Some providers add media URLs or the link to the post on X. The timeline goes back at most a few hundred posts or a few months, depending on the provider.

How a Joshu assistant uses it

Before a sales call with the founder of a company, Joshu pulls their recent X posts and notes the two or three that could come up in conversation: a product launch, a hiring announcement, or an opinion on the industry.

When you ask Joshu to research someone before writing an intro or an outreach email, it checks their X timeline to see what they have been talking about lately, then drafts the email with a personal opening line.

Every Monday, Joshu can pull the timeline of three or four people in your industry and send you a digest of the posts that mention topics you care about.

Choosing a provider

Providers differ in how far back the timeline goes and in which fields the reply includes. Pick a cheaper endpoint when you only need the text and engagement counts for the most recent posts. Choose one with media URLs or richer metadata when you want to know what the person shared or quote their exact words with a link.

Call it

This example calls X / Twitter User Tweets and Replies. Each endpoint takes its own inputs, which its page lists. A Joshu assistant makes the same call with its own token.

Router call with a router API key
curl https://hello.joshu.me/api/router/call \
  -H "Authorization: Bearer $JOSHU_ROUTER_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "endpoint": "anyapi.x.user.posts",
    "params": {
      "limit": 20,
      "handle": "username"
    }
  }'