/producthunt/users

POST /api/producthunt/users

Price: 5 credits

Get Product Hunt (producthunt.com) user profile by username or profile URL

How to use it

Get a Product Hunt (producthunt.com) user profile by username (with or without leading @) or by full profile URL. Returns id, name, alias, headline, image, header_image, follower/following counts, submitted_post_count, product_count, review_count, day_streak, Kitty Points rankings (monthly/yearly/all-time rank + KP), badges (achievements), links (social), and a short list of products the user is a featured maker of.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — Product Hunt username ('kevin', '@kevin') or full profile URL ('https://www.producthunt.com/@kevin'). (examples: "jakecrump", "@kevin", "https://www.producthunt.com/@rrhoover"; minLength: 1; pattern: ^(?:https?://[^\s]+|//[^\s]+|(?:www\.)?producthunt\.com[^\s]*|@?[A-Za-z0-9][A-Za-z0-9._-]*)$)

Response

• @type string (default: "ProductHuntUser")
• id string required
• alias string required
• name string required
• headline string nullable
• url string required
• image string nullable
• header_image string nullable
• is_verified boolean nullable
• is_maker boolean nullable
• follower_count integer nullable
• following_count integer nullable
• submitted_post_count integer nullable
• product_count integer nullable
• collection_count integer nullable
• stack_count integer nullable
• review_count integer nullable
• day_streak integer nullable
• twitter_username string nullable
• kp_month object nullable
  • @type string (default: "ProductHuntUserKittyCoin")
  • rank integer nullable
  • kp number nullable
• kp_year object nullable
  • @type string (default: "ProductHuntUserKittyCoin")
  • rank integer nullable
  • kp number nullable
• kp_all_time object nullable
  • @type string (default: "ProductHuntUserKittyCoin")
  • rank integer nullable
  • kp number nullable
• links array (default: [])
  • @type string (default: "ProductHuntUserLink")
  • id string nullable
  • kind string nullable
  • name string nullable
  • url string required
• badges array (default: [])
  • @type string (default: "ProductHuntUserBadge")
  • id string nullable
  • kind string nullable
  • name string required
  • description string nullable
  • count integer nullable
  • image string nullable
• products array (default: [])
  • @type string (default: "ProductHuntUserProduct")
  • id string required
  • name string required
  • alias string nullable
  • tagline string nullable
  • image string nullable
  • url string nullable
  • is_offline 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 — User not found 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.