/xdaforums/threads/posts

POST /api/xdaforums/threads/posts

Price: 10 credits

Get the posts of an XDA Forums thread in thread order: post number, author with title, join date and message count, post time, last edit time, plain text, images, links, quoted post ids and reactions.

How to use it

Read a thread's discussion from the first post onward; count caps how many posts come back and the walk stops at the thread's last page. quoted_post_ids point at other posts in the returned list, which lets you rebuild reply chains.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• thread string required — XDA Forums thread id or thread URL (examples: "4482089", "https://xdaforums.com/t/psa-android-13-bootloader-anti-rollback.4482089/"; minLength: 1)
• count integer required — Max number of posts to return (min: 1)

Response

• @type string (default: "XdaforumsThreadsPost")
• id string required
• number integer nullable
• thread_id string required
• url string required
• author object nullable
  • @type string (default: "XenforoMember")
  • id string nullable
  • alias string nullable
  • name string required
  • url string nullable
  • image string nullable
  • user_title string nullable
  • joined_at integer nullable
  • messages_count integer nullable
  • solutions_count integer nullable
  • reaction_score integer nullable
  • location string nullable
  • devices array (default: [])
• created_at integer nullable
• updated_at integer nullable
• text string nullable
• images array (default: [])
• links array (default: [])
• attachments array (default: [])
  • @type string (default: "XenforoAttachment")
  • id string nullable
  • name string nullable
  • url string required
  • image string nullable
  • size_bytes integer nullable
  • view_count integer nullable
• quoted_post_ids array (default: [])
• reactions array (default: [])
• reaction_count integer nullable
• is_thread_starter boolean (default: false)

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 thread with this id, or the thread is not visible to a logged-out visitor 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.