/indiehackers/products

POST /api/indiehackers/products

Price: 1 credit

Get an Indie Hackers product by slug or URL

How to use it

Get a single Indie Hackers product by slug (e.g. 'wysera') or product URL. Returns id, name, tagline, description, revenue (self-reported or Stripe-verified monthly revenue in USD), is_revenue_verified, follower_count, website_url, image, twitter_handle, facebook_url, verticals, revenue_models, funding, platforms, employees, commitment, founders_type, founders_can_code, start_date, end_date, user_ids, resolved founders, and timestamps.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Product slug or product URL (examples: "wysera", "https://www.indiehackers.com/product/wysera"; minLength: 1)

Response

• @type string (default: "IndiehackersProduct")
• id string required
• name string required
• tagline string nullable
• description string nullable
• revenue number nullable
• is_revenue_verified boolean (default: false)
• follower_count integer nullable
• website_url string nullable
• image string nullable
• twitter_handle string nullable
• facebook_url string nullable
• verticals array (default: [])
• revenue_models array (default: [])
• funding array (default: [])
• platforms array (default: [])
• employees string nullable
• commitment string nullable
• founders_type string nullable
• founders_can_code boolean nullable
• start_date string nullable
• end_date string nullable
• user_ids array (default: [])
• founders array (default: [])
  • @type string (default: "IndiehackersUserBrief")
  • id string required
  • alias string nullable
  • full_name string nullable
  • bio string nullable
  • twitter_handle string nullable
• created_at integer nullable
• published_at integer nullable
• updated_at integer nullable
• approved_at integer nullable
• bumped_at integer nullable
• product_url string 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 — Product not found. Verify the slug or URL. 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.