/steamdb/apps

POST /api/steamdb/apps

Price: 1 credit

Get SteamDB (steamdb.info) application details by Steam app ID

How to use it

Get full SteamDB intelligence for a Steam application by its numeric app ID. Returns name, type, developer/publisher, technologies, release date, primary genre, store genres, franchise, alternative names, Steam Deck compatibility, tags, categories, SteamDB rating with positive/negative review counts, current and 24-hour-peak player counts, current and lowest recorded US price, and package/DLC/depot counts.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• appid integer required — Steam application ID (examples: 730, 620, 1245620; >: 0)

Response

• @type string (default: "SteamdbApp")
• app_id integer required
• name string required
• url string required
• app_type string nullable
• description string nullable
• image string nullable
• developer string nullable
• publisher string nullable
• technologies string nullable
• supported_systems string nullable
• release_date string nullable
• last_changenumber integer nullable
• primary_genre string nullable
• genres array (default: [])
• franchise string nullable
• aliases array (default: [])
• steam_deck_compatibility string nullable
• tags array (default: [])
• categories array (default: [])
• rating number nullable
• rating_desc string nullable
• positive_review_count integer nullable
• negative_review_count integer nullable
• review_count integer nullable
• players_now integer nullable
• peak_24h integer nullable
• peak_all_time integer nullable
• price object nullable
  • @type string (default: "SteamdbAppPrice")
  • currency string required
  • current_price string nullable
  • converted_price string nullable
  • lowest_price string nullable
• package_count integer nullable
• dlc_count integer nullable
• depot_count integer nullable
• steam_store_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 — 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.