How is this different from the official X (Twitter) API?

The official X API requires a developer account, an app registration, OAuth, and paid tiers that start at $100/month with strict read caps. This API needs none of that: sign up at apicodex.io/register, send a GET request with a URL or username, and get JSON back. It covers public post and profile data, starts free, and bills simple pay-per-use overage.

What data can it access? Is it compliant?

Only publicly visible data: public posts, public profile info and public recent posts. It cannot read protected accounts, DMs or anything behind a login, and it never asks for user credentials. You remain responsible for using the data in line with applicable laws and your own compliance requirements.

How fresh is the data?

Live. Every call performs a fresh scrape of x.com at request time, so follower counts, likes, reposts and recent posts reflect the current state of the page rather than a cached snapshot.

What does a 202 response mean and what do I do with it?

Most calls resolve synchronously in 2-45 seconds. If a scrape exceeds the sync window, the API returns HTTP 202 with {"status": "pending", "snapshot_id": "..."}. Poll GET /v1/result?snapshot_id=... until it returns status "ready" with the data, typically within 1-2 minutes.

Do I have to pass full URLs, or can I use usernames?

On /v1/profile and /v1/profile-posts you can pass ?username=jack instead of a URL, with or without a leading @ (it is stripped automatically). /v1/post always takes the post URL (x.com/ /status/...), since a post is identified by its URL.

What are the rate limits and plan sizes?

Basic (free) includes 25 requests/month at 1 req/s with a hard cap. Pro is $19.99 for 1,000 requests/month at 5 req/s, Ultra $49.99 for 5,000 at 10 req/s, and Mega $199.99 for 50,000 at 20 req/s. Paid plans allow overage at $0.02, $0.012 and $0.006 per request respectively, so the unit cost drops as you upgrade.

Tweets, profiles and recent posts as clean JSON

Advanced X (Twitter) API

The official X API starts at $100/month and still gates most data behind strict caps. The Advanced X (Twitter) API is the simple alternative for public data: pass a post URL, a profile URL or just a username and get structured JSON back in one request. Post text, author, engagement metrics, media, follower counts, bio and verification, no developer account and no OAuth.

Every call performs a live scrape, so you always get current data instead of a stale cache. Get a single tweet, a full profile, or up to 50 recent posts per profile. Use the fields parameter to keep only the keys you need.

Get a free API key Read the docs

Free tier included, no credit card required. One key works across every API.

Free calls / month: 40
Endpoints: 4
Response Time: 2-45s
Data Freshness: Live

Get your free API key

40 free calls on the free plan

Key features

Single post by URL: text, author, engagement metrics, media, date
Profile info: id, name, biography, followers, following, posts_count, is_verified
Recent posts per profile (limit 1-50, default 10)
Pass a username instead of a URL (leading @ accepted)
fields parameter to select only the keys you need
No X developer account, no OAuth, no $100/mo official tier

Built for

Social listening and brand monitoring
Sentiment analysis on posts and replies
Influencer vetting and audience research
Lead enrichment with live profile data

MCP · for your agent

Hand the Advanced X (Twitter) API to your agent

Connect Claude, Cursor or any MCP client once, then ask in plain words. Your agent finds this API, reads its docs and makes the call: 25 credits per call, the same as REST, from your team's balance.

Connect your agent

Monitor a competitor's announcements

“What has Globex announced on X and LinkedIn this week? Summarize anything about pricing or new features.”

list_apis · get_api_docsfree

api_request GET /twitter/v1/profile-posts?username=globex&limit=20 25 cr

+ Advanced LinkedIn API25 cr

Their latest posts from both networks with engagement, and the pricing and feature news pulled out.

Report on a launch post

“Our launch post on X is taking off. Pull its likes, reposts and replies so I can add them to the launch report.”

list_apis · get_api_docsfree

api_request GET /twitter/v1/post?url=https://x.com/acmehq/status/1843000000000000000 25 cr

Current likes, reposts and replies with the post date, formatted for the launch report.

Size up a co-marketing partner

“We're co-hosting a webinar with Initech. How big is their audience on X, and is the account verified?”

list_apis · get_api_docsfree

api_request GET /twitter/v1/profile?username=initech 25 cr

Followers, following, post count, bio and verification status for the account.

$ claude mcp add --transport http apicodex https://mcp.apicodex.io

Illustrative asks; the calls and prices are real. Claude, Cursor, VS Code and Windsurf setup: mcp.apicodex.io

Try it

Build the request for your data

Edit the parameters below and see the exact request and curl command you'd send. No key required to preview.

GET /twitter/v1/post

Open in Playground

Parameters

url

Request · HTTP

GET /twitter/v1/post?url=https://x.com/jack/status/20 HTTP/1.1
Host: api.apicodex.io
X-Api-Key: YOUR_API_KEY

Response · JSON 200 OK

{
  "type": "post",
  "url": "https://x.com/jack/status/20",
  "data": {
    "id": "20",
    "user_posted": "jack",
    "name": "jack",
    "description": "just setting up my twttr",
    "date_posted": "2006-03-21T20:50:14.000Z",
    "replies": 12000,
    "reposts": 130000,
    "likes": 195000,
    "photos": [],
    "url": "https://x.com/jack/status/20"
  }
}

Run it with your key

Documentation

Advanced X (Twitter) API Documentation

Pass an X (Twitter) post URL, a profile URL, or simply a username and get structured JSON back in a single request: post text, author, engagement metrics, media, full profile info and recent posts. A fresh scrape usually returns in 2-45 seconds; heavy calls may return HTTP 202 with a snapshot_id you resolve via /v1/result.

Base URL

url

https://api.apicodex.io/twitter

Authentication

Create a key at apicodex.io/register and send it as an X-Api-Key header (or an ?apikey= query parameter) on every request. Calls without a valid key return 401.

headers

GET /twitter/v1/profile?username=jack
X-Api-Key: YOUR_API_KEY

Request and response

Illustrative values. Confirm current endpoint behavior, quotas, and data freshness in the API documentation before production use.

request · http

GET /twitter/v1/post?url=https://x.com/jack/status/20 HTTP/1.1
Host: api.apicodex.io
X-Api-Key: YOUR_API_KEY

response · json

{
  "type": "post",
  "url": "https://x.com/jack/status/20",
  "data": {
    "id": "20",
    "user_posted": "jack",
    "name": "jack",
    "description": "just setting up my twttr",
    "date_posted": "2006-03-21T20:50:14.000Z",
    "replies": 12000,
    "reposts": 130000,
    "likes": 195000,
    "photos": [],
    "url": "https://x.com/jack/status/20"
  }
}

Code examples

cURL

curl --request GET \
  --url 'https://api.apicodex.io/twitter/v1/profile?username=jack' \
  --header 'X-Api-Key: YOUR_API_KEY'

JavaScript/Node.js

const res = await fetch('https://api.apicodex.io/twitter/v1/profile?username=jack', {
  headers: {
    'X-Api-Key': 'YOUR_API_KEY'
  },
});
console.log(await res.json());

Python

import requests

url = "https://api.apicodex.io/twitter/v1/profile"
querystring = {"username": "jack"}
headers = {
    "X-Api-Key": "YOUR_API_KEY"
}
print(requests.get(url, headers=headers, params=querystring).json())

Available Endpoints

GET /v1/post

Scrape a single post by URL: text, author, engagement metrics, media, date.

/v1/post?url=https://x.com/jack/status/20

GET /v1/profile

Profile info by url or username: id, name, biography, followers, following, posts_count, is_verified.

/v1/profile?username=jack

GET /v1/profile-posts

Recent posts of a profile as an array (limit 1-50, default 10).

/v1/profile-posts?username=jack&limit=10

GET /v1/result

Fetch a pending result after a 202 response, using its snapshot_id.

/v1/result?snapshot_id=s_abc123

Request Parameters

Required parameters

url Post URL on /v1/post (x.com/<user>/status/...). On profile endpoints, either url or username is required.

Optional parameters

username On /v1/profile and /v1/profile-posts, pass a username instead of url. A leading @ is stripped automatically.
limit /v1/profile-posts only: max recent posts to return (1-50, default 10).
fields Comma-separated list of top-level fields to keep in data, e.g. fields=id,followers,biography. Works on single objects and arrays.
snapshot_id /v1/result only: the id returned by a 202 response.

Responsible use

Use public social data carefully

Only request data that is publicly accessible, and make sure your collection, storage, and use comply with applicable privacy laws and the relevant platform terms. Do not use these APIs to bypass access controls or to make decisions that require consent or human review.

Pricing

Advanced X (Twitter) API Pricing

This API costs 25 credits per request. Credits are shared across every API on your plan.

Estimate your monthly cost

Drag the slider to match your expected request volume. We'll recommend the cheapest plan that covers it.

Requests per month 10,000

Recommended plan

Starter

$29.99 /month

Credits used

Credits included

Cost per 1K requests

Choose Starter

Free

1,000 credits · ~40 requests/mo · 2 rps

All APIs included
No credit card required
Full documentation and examples
MCP server for your AI agents
Up to 5 active API keys

Start for free

Starter

Popular

$29.99 /month

50,000 credits · ~2,000 requests/mo · 10 rps

All APIs included
Email support
Usage dashboard and analytics
MCP server for your AI agents
Up to 5 active API keys

Start with Starter

Pro

$99.99 /month

250,000 credits · ~10,000 requests/mo · 25 rps

All APIs included
Priority support
MCP server for your AI agents
Up to 5 active API keys

Start with Pro

FAQ

Advanced X (Twitter) API

Key features

Built for

Hand the Advanced X (Twitter) API to your agent

Monitor a competitor's announcements

Report on a launch post

Size up a co-marketing partner

Build the request for your data

Advanced X (Twitter) API Documentation

Base URL

Authentication

Request and response

Code examples

Available Endpoints

GET /v1/post

GET /v1/profile

GET /v1/profile-posts

GET /v1/result

Request Parameters

Required parameters

Optional parameters

Use public social data carefully

Advanced X (Twitter) API Pricing

Free

Starter

Pro

Need a different plan?

Frequently asked questions

Related APIs