/macrumors/articles

POST /api/macrumors/articles

Price: 5 credits

Get a MacRumors news article by URL or date path: headline, summary, full body text, section, author with bio, publish time, images, reader comment count, the forum discussion thread id and the top reader comments embedded in the page.

How to use it

Fetch one MacRumors news story. The reader discussion lives on the MacRumors forum: discussion_thread_id is the forum thread id for reading all of it.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• article string required — MacRumors article URL or its date path (yyyy/mm/dd/slug) (examples: "https://www.macrumors.com/2026/09/10/apple-watch-ultra-4-glonass/", "2026/09/10/apple-watch-ultra-4-glonass"; minLength: 1)

Response

• @type string (default: "MacrumorsArticle")
• alias string required
• url string required
• article_title string required
• description string nullable
• text string nullable
• section string nullable
• language string nullable
• published_at integer nullable
• author object nullable
  • @type string (default: "MacrumorsAuthorRef")
  • alias string nullable
  • name string required
  • url string nullable
  • social_url string nullable
  • description string nullable
• image string nullable
• images array (default: [])
• comment_count integer nullable
• discussion_url string nullable
• discussion_thread_id string nullable
• comments array (default: [])
  • @type string (default: "MacrumorsArticleComment")
  • author_name string nullable
  • created_at integer nullable
  • text string required
  • url string nullable
  • upvote_count integer 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 at this path 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.