/steamdb/sales

POST /api/steamdb/sales

Price: 5 credits

Get the current SteamDB (steamdb.info) list of discounted Steam games

How to use it

Get the list of Steam games currently on sale. Each entry has the game name, Steam app ID, discount percent, current sale price, deal type, SteamDB rating, release date, whether the price is at a historical low, and when the sale started and ends. Set count to control how many discounted games to return, and min_discount to require a minimum discount.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Number of discounted games to return (min: 1)
• min_discount integer nullable — Only return games discounted at least this percent (min: 1; max: 100)

Response

• @type string (default: "SteamdbSale")
• app_id integer required
• name string required
• url string required
• image string nullable
• discount_percent integer required
• price_current string nullable
• deal_type string nullable
• rating number nullable
• release_date string nullable
• is_historical_low boolean (default: false)
• steam_store_url string nullable
• ends_at string nullable
• started_at 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 — 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.