/xdaforums/boards/threads

POST /api/xdaforums/boards/threads

Price: 5 credits

List the threads of an XDA Forums board: title, prefix, starter, start time, last message time and poster, reply and view counts, first-post reaction score, page count and sticky/locked flags. Filters by prefix, starter, recent activity and thread type, and sorts by any of the forum's sort fields.

How to use it

Browse a device board's threads. Sticky threads come first on the opening page and carry is_sticky. prefix_id is checked against the board's own prefix list and an unknown one is rejected, because the forum itself would silently ignore it. View counts are rounded by the forum (for example 1K).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• board string required — Board id or board URL (examples: "12311", "https://xdaforums.com/f/google-pixel-6.12311/"; minLength: 1)
• count integer required — Max number of threads to return (min: 1)
• prefix_id integer nullable — Only threads carrying this board prefix; must be one of the board's own prefixes (examples: 33)
• starter_id integer nullable — Only threads started by this member id (examples: 3690504)
• last_days integer nullable — Only threads with a message in the last N days (one of: 7, 14, 30, 60, 90, 182, 365; examples: 30)
• thread_type string nullable — Only discussions or only polls (one of: "discussion", "poll")
• order string nullable — Sort field; the forum sorts by last message when omitted (one of: "last_post_date", "post_date", "title", "reply_count", "view_count", "first_post_reaction_score")
• direction string nullable — Sort direction; descending when omitted (one of: "desc", "asc")

Response

• @type string (default: "XdaforumsBoardsThread")
• id string required
• alias string nullable
• url string required
• thread_title string required
• prefix string nullable
• prefix_id string nullable
• 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
• last_post_at integer nullable
• last_poster 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: [])
• reply_count integer nullable
• view_count integer nullable
• first_post_reaction_score integer nullable
• page_count integer nullable
• is_sticky boolean (default: false)
• is_locked boolean (default: false)

Errors

• 422 — prefix_id is not one of the board's prefixes 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 board with this id 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.