/producthunt/forums/search

POST /api/producthunt/forums/search

Price: 5 credits

Search Product Hunt (producthunt.com) forum threads — global trending/recent feed, per-forum listing, or keyword-filtered search

How to use it

Search Product Hunt (producthunt.com) forum threads (discussions under /p/<forum>). Without filters returns the global feed sorted by `sort` (trending or recent). Set `forum` to scope to one forum (slug like 'general' or 'notion'). Set `keyword` for cross-forum keyword search. `forum` and `keyword` cannot be combined. Returns id, alias, title, text, url, author, forum (slug + category), upvote/comment counts, created_at.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• forum string nullable — Forum slug ('general', 'notion') or forum URL ('https://www.producthunt.com/p/general'). If set, listing is scoped to this forum. (examples: "general", "notion", "https://www.producthunt.com/p/general"; pattern: ^(?:https?://[^\s]+|//[^\s]+|(?:www\.)?producthunt\.com[^\s]*|[A-Za-z0-9][A-Za-z0-9._-]*)$)
• keyword string nullable — Filter threads by keyword across all forums. Cannot be combined with `forum` filter. (examples: "notion", "blockchain", "launch"; minLength: 1)
• sort string — Sort order for the global threads feed. Ignored when `forum` or `keyword` is set. (default: "trending"; one of: "trending", "recent")
• count integer required — Max number of threads to return (min: 1)

Response

• @type string (default: "ProductHuntForumsSearchThread")
• id string required
• alias string required
• text string nullable
• url string required
• author object nullable
  • @type string (default: "ProductHuntForumUser")
  • id string nullable
  • name string nullable
  • alias string nullable
  • image string nullable
  • is_verified boolean nullable
  • is_ambassador boolean nullable
  • is_prominent boolean nullable
• forum object nullable
  • @type string (default: "ProductHuntForum")
  • id string nullable
  • alias string required
  • name string nullable
  • description string nullable
  • category_id string nullable
  • category_alias string nullable
  • category_name string nullable
• created_at string nullable
• vote_count integer nullable
• comment_count integer nullable
• is_featured boolean nullable
• is_pinned boolean nullable

Errors

• 422 — Invalid forum input or `forum` combined with `keyword` 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 — The entity was not found, or a precondition failed 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.