/indiehackers/users

POST /api/indiehackers/users

Price: 5 credits

Get an Indie Hackers member profile by username, with the member's 20 most recent public activity items

How to use it

Look up one Indie Hackers member by the username that appears in a profile URL, such as uptownhr. Returns the display name, bio, avatar and the member's recent activity: at most the 20 latest posts the member wrote or commented on, each with its title, permalink and timestamp, and fewer when the member has been active fewer times. Activity older than those 20 items is not returned. Take the username from an author field in indiehackers/posts/search or from the people list of indiehackers/products.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — Indie Hackers username or profile URL (examples: "uptownhr", "https://www.indiehackers.com/channingallen"; minLength: 1)

Response

• @type string (default: "IndiehackersUser")
• id string required
• alias string required
• user_id string nullable
• full_name string nullable
• bio string nullable
• image string nullable
• profile_url string nullable
• activity array (default: [])
  • @type string (default: "IndiehackersUserActivity")
  • post_id string required
  • action string nullable
  • post_title string nullable
  • post_url string nullable
  • created_at 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 Indie Hackers member with this username. 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.