/xda/articles

POST /api/xda/articles

Price: 10 credits

Get an XDA article by slug or URL: headline, summary, full body text, publish and modified time, authors with job title and bio, topics, categories, images, reviewed products with price and store link, reader comment count and whether it is free to read.

How to use it

Fetch one XDA story, review or guide. products is filled on reviews and buying guides and carries the listed price and retailer link.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• article string required — XDA article URL or its slug (examples: "google-pixel-11-pro-review", "https://www.xda-developers.com/google-pixel-11-pro-review/"; minLength: 1)

Response

• @type string (default: "XdaArticle")
• alias string required
• url string required
• article_title string required
• description string nullable
• text string nullable
• published_at integer nullable
• updated_at integer nullable
• authors array (default: [])
  • @type string (default: "XdaAuthorRef")
  • alias string nullable
  • name string required
  • url string nullable
  • image string nullable
  • job_title string nullable
  • description string nullable
  • social_urls array (default: [])
• topics array (default: [])
• categories array (default: [])
• image string nullable
• images array (default: [])
• products array (default: [])
  • @type string (default: "XdaProduct")
  • name string required
  • brand string nullable
  • description string nullable
  • image string nullable
  • price number nullable
  • currency string nullable
  • offer_url string nullable
  • offers array (default: [])
    • @type string (default: "XdaOffer")
    • price number nullable
    • currency string nullable
    • url string nullable
• comment_count integer nullable
• is_accessible_for_free boolean nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No article with this slug, or the slug belongs to a section, tag or author page Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.