Skip to main content
GET https://xquik.com/api/v1/x/articles/{tweetId}
5 credits per call · All plans from $0.00012/creditDirect MPP at USD 0.00075 per call
Get X Article returns one long-form X Article by wrapper tweet ID. The endpoint is GET /api/v1/x/articles/{tweetId}.
The examples build article rows, not raw lookup dumps. Use GET /api/v1/x/articles/{tweetId} when a workflow needs one long-form post body plus article metadata. Store tweet_id, article_title, preview_text, author_id, author_username, author_name, author_profile_picture, created_at, cover_image_url, body_text, and body_markdown. Keep these fields with the record you pass on. Your archive, article index, or agent handoff may need block-level completeness and formatting checks. If so, store block_count, block_types, formatted_blocks, and media_urls.

Find candidate articles

This endpoint needs the numeric wrapper tweet ID of an X Article. When a workflow starts from a mixed set of tweets, search first. Then store candidate tweet IDs and try the article lookup once per candidate.

Search first

Search tweets finds candidate wrapper tweets by author, keyword, URL, or visible tweet text.

Article lookup

Call GET /api/v1/x/articles/{tweetId} with the candidate tweet ID when the workflow needs the long-form body.

Fallback route

If you get article_not_found, store the terminal result and switch to Get tweet or Get tweet thread.

Saved export

Use article_extractor for an extraction job, estimate, or CSV, JSON, or XLSX export.

Direct article handoff

Use GET /api/v1/x/articles/{tweetId} when you need the article body and have its tweet ID. That ID is the numeric tweet ID of an X Article wrapper tweet. Use the final status ID from an X Article URL. A normal tweet ID can be valid. It can still return 404 article_not_found when it is not an X Article.

Article row

Store article.title, previewText, coverImageUrl, createdAt, metrics, and a derived body_text field.

Body blocks

Store article.contents[] for headings, lists, quotes, media, dividers, code blocks, and inline styles.

Author joins

Store author.id, username, name, and profilePicture when returned.

Media assets

Store coverImageUrl and media-block url values for article archives and article review.

Not an article

article_not_found is final for that tweet ID. Ask for an X Article URL or use a tweet or thread endpoint.

Saved exports

Use article_extractor for a saved extraction job or CSV, JSON, or XLSX export.

Store an X article archive

Keep the wrapper Tweet ID, article fields, structured content blocks, and author. Keep the cover image and collection time. Keep article.contents[] when the archive must reconstruct headings, lists, quotes, media, dividers, or code.Direct article reads cost 5 credits per successful call. For MPP callers, this endpoint bills a fixed charge of USD 0.00075 per call.

Path parameters

Which article endpoint?

X article body

Use GET /x/articles/{tweetId} for one X Article. It returns the title, body blocks, cover image, metrics, and author fields.

Single tweet

Use Get tweet for one tweet’s text, media, author, and engagement metrics.

Tweet thread

Use Get tweet thread for conversation context around the article wrapper tweet.

Search tweets

Use Search tweets to discover candidate article tweets by keyword, URL, author, or other filters.

Saved exports

Use Create extraction with toolType=article_extractor for a saved job or CSV, JSON, or XLSX export.

Article-not-found handling

Do not retry the same ID after article_not_found. Switch to tweet lookup or ask for an X Article URL.

Query parameters

Headers

Response

200 OK

400 Invalid tweet ID

{ "error": "invalid_tweet_id" } The provided tweet ID is empty or not a valid format.

401 Unauthenticated

Missing or invalid API key. Check the x-api-key header value.

402 Payment required

Account keys get account options. Guest keys get guest top-up only. Anonymous calls receive a direct MPP WWW-Authenticate: Payment challenge plus a guest wallet creation action. No checkout starts automatically. Confirm any payment action.

404 Article not found

The tweet is valid but does not contain an X Article.

502 X API unavailable

The read service returned an error. Retry after a short delay.

429 Rate limit exceeded

You exceeded your tier rate limit. Wait for the Retry-After header before retrying.

424 Dependency failed

The normalized v1 response contract can return 424 when the read service is unavailable.

Response examples

  • 400 { "error": "invalid_input", "message": "Invalid input. Check the request body." }
  • 401 { "error": "unauthenticated", "message": "Authentication required. Provide a valid API key or bearer token." }
  • 402 { "error": "insufficient_credits", "message": "Insufficient credits. Top up or subscribe to continue." }
  • 403 { "error": "api_key_paused", "message": "This API key is paused. Resume it at dashboard.xquik.com/api-keys to use it again." }
  • 404 { "error": "article_not_found", "message": "Article not found. Use an X Article tweet ID." }
  • 424 { "error": "x_api_unavailable", "message": "X data source temporarily unavailable. Try again later." }
  • 429 { "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 }
  • 502 { "error": "x_api_unavailable", "message": "X data source temporarily unavailable. Try again later." }
  • 503 { "error": "x_api_unavailable", "message": "Xquik is busy right now. Retry shortly." }