Get Article API | Read a Published or Your Own Draft X Article

Get Article reads an article's full content (title, content_state, cover media, author). Two mutually exclusive forms: id or url (the announcement tweet) for a public read of any Published article, needing only the API key; or article_id (the article's own entity id) for an owner-only read that requires a registered session and also reaches your own Drafts. It returns 404 when not found, not visible, or not owned by the caller.

curl -X GET "https://example.com/article/get?id=2086650300012345678&url=https%3A%2F%2Fx.com%2Fi%2Fstatus%2F2086650300012345678&article_id=QXJ0aWNsZUVudGl0eToyMDg2NjUwMjI4OTUwNjgzNjQ4"

{  "id": "2086650300012345678",  "article": {    "id": "QXJ0aWNsZUVudGl0eToyMDg2NjUwMjI4OTUwNjgzNjQ4",    "rest_id": "2086650228950683648",    "title": "Why we rebuilt our onboarding from scratch",    "preview_text": "Opening paragraph.",    "lifecycle": "Published",    "content_state": {      "blocks": [        {          "key": "a1b2c",          "text": "Opening paragraph.",          "type": "unstyled",          "depth": 0,          "inlineStyleRanges": [],          "entityRanges": []        }      ],      "entityMap": []    },    "cover_media": null,    "media_entities": [],    "author": {      "id": "44196397",      "username": "elonmusk",      "name": "Elon Musk"    },    "created_at_secs": 1786400000,    "modified_at_secs": 1786400400,    "first_published_at_secs": 1786400400,    "visibility_setting": "Public",    "tweet_id": "2086650300012345678",    "public_url": "https://x.com/i/article/2086650228950683648"  }}

{  "error": "bad_request",  "message": "Missing or malformed parameter. Fix the request before retrying."}

{  "error": "unauthorized",  "message": "The API key is missing, malformed, or revoked. Check the Authorization header."}

{  "error": "insufficient_credits",  "message": "Your balance is exhausted. Top up your credits to continue."}

{  "error": "not_found",  "message": "The resource does not exist, for example a deleted tweet or a private account."}

{  "error": "rate_limited",  "message": "Too many requests. Back off and retry with exponential backoff."}

{  "error": "server_error",  "message": "Something failed on our side. Retry with backoff; if it persists, contact support."}

Pricing

When to use

Use the id/url form to read any published article you have the announcement tweet for, including ones you do not own. Use the article_id form when you already hold an entity id from Article Create or Article List and want to read that specific article again, including a Draft. To enumerate your own articles from scratch instead of reading one you already have an id for, use Article List.

Notes

• PUBLIC form (id/url): no customer session or per-call inline credentials needed, just the API key. 404 ("No article found at that tweet id/URL") covers three cases alike: the tweet was deleted, the account is protected, or the tweet exists but is not an article announcement. Only reaches PUBLISHED articles.
• OWNER-ONLY form (article_id): requires a registered session (POST /customer/session) or per-call inline credentials. Also reaches your own Drafts, which have no announcement tweet the public form could resolve. No dedicated get-by-id operation exists upstream, so this scans your own Draft then Published lists and matches on the id you provided, the same lookup Article Delete already does internally.

Related endpoints

• List Articles: List your own articles, filtered by lifecycle (draft or published).
• Create Article: Start a new draft article. No request body required.
• Publish Article: Publish a draft article. This posts a real, public announcement tweet.
• Tweet Detail: Fetch a single tweet's full object by ID.

FAQ

Do I need a registered session to read an article?

Only for the article_id form. The id/url form is a public pooled read, exactly like Tweet Detail: it only needs your API key. The article_id form is owner-only and requires a registered session or per-call inline credentials, the same as Article List.

What happens if the tweet is not an article announcement, or the article_id is not found?

Either way you get a 404 and article comes back null rather than an error body. For id/url that covers the tweet being deleted, protected, or not an article announcement. For article_id it covers the id not existing or not belonging to the calling account, the same as twitterapi.io's contract, which does not distinguish the two either.

Can I read my own draft this way?

Yes, with the article_id form, since it is owner-only and does not depend on an announcement tweet (a draft has none). The id/url form cannot reach a draft for the same reason: there is no public tweet to resolve.