/steam/apps/search

POST /api/steam/apps/search

Price: 1 credit

Search Steam apps by term, keyword, or franchise

How to use it

Search the Steam store for apps by term, keyword, or franchise. Set count to how many results you want. Each item has id, type, name, price and currency, supported platforms, Metacritic score, controller support, streaming-video flag, and capsule image. Use cc to select the storefront country (controls price, currency and regional catalog).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• term string required — Search term — an app name, keyword, or franchise (examples: "counter strike", "portal"; minLength: 1)
• count integer required — Max number of results to return (min: 1; max: 10)
• cc string — Storefront country (controls price, currency and region) (default: "us"; one of: "us", "gb", "ca", "au", "de", "fr", "it", "es", "nl", "se", "jp", "kr", "cn", "in", "br", "mx", "ru", "tr", "pl", "ae", "sa", "sg", "hk", "tw", "id", "th", "vn", "ph", "my", "za")
• language string — Language for localized text fields (default: "en"; minLength: 2)

Response

• @type string (default: "SteamSearchApp")
• id integer required
• type string nullable
• name string required
• image string nullable
• price object nullable
  • @type string (default: "SteamSearchPrice")
  • currency string nullable
  • initial integer nullable
  • final integer nullable
• platforms object nullable
  • @type string (default: "SteamSearchPlatforms")
  • windows boolean (default: false)
  • mac boolean (default: false)
  • linux boolean (default: false)
• metascore integer nullable
• controller_support string nullable
• streamingvideo boolean (default: false)

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 — The entity was not found, or a precondition failed 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.