/steam/apps/reviews

POST /api/steam/apps/reviews

Price: 5 credits

Get Steam app user reviews by app ID

How to use it

Get user reviews of a Steam app by its numeric app ID or store URL. Returns each review's author (Steam ID, display name, avatar, online status, profile URL, games owned, review count, playtime), language, text, whether it is positive, helpful and funny vote counts, comment count, weighted vote score, whether it was a Steam purchase or received for free, whether it was written during early access, whether it was refunded, whether it was made primarily on Steam Deck, award reactions, created/updated timestamps, and the app's release date. Use review_type to filter by sentiment (all, positive, negative) and language to filter by review language.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• appid string required — Steam app ID (numeric) or store URL (examples: "730", "1086940"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)
• review_type string — Filter reviews by sentiment (default: "all"; one of: "all", "positive", "negative")
• language string — Review language filter (default: "all"; minLength: 1)

Response

• @type string (default: "SteamReview")
• id string required
• author object nullable
  • @type string (default: "SteamReviewAuthor")
  • steamid string nullable
  • name string nullable
  • image string nullable
  • persona_status string nullable
  • profile_url string nullable
  • game_count integer nullable
  • review_count integer nullable
  • playtime_forever integer nullable
  • playtime_last_two_weeks integer nullable
  • playtime_at_review integer nullable
  • last_played integer nullable
• language string nullable
• text string nullable
• is_positive boolean (default: false)
• helpful_count integer nullable
• funny_count integer nullable
• comment_count integer nullable
• weighted_vote_score number nullable
• is_steam_purchase boolean (default: false)
• is_received_for_free boolean (default: false)
• is_written_during_early_access boolean (default: false)
• is_refunded boolean (default: false)
• is_primarily_steam_deck boolean (default: false)
• reactions array (default: [])
  • @type string (default: "SteamReviewReaction")
  • reaction_type integer nullable
  • count integer nullable
• created_at integer nullable
• updated_at integer nullable
• released_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 — App 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.