/steam/packages

POST /api/steam/packages

Price: 20 credits

Get Steam package (bundle/sub) details by package ID

How to use it

Get details of a Steam package (a bundle or sub that groups one or more apps) by its numeric package ID or store URL. Returns name, price and currency, discount, the list of apps included in the package, supported platforms, release date, controller support, descriptive text, and images. Use cc to select the storefront country (controls price and currency).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• packageid string required — Steam package ID (numeric) or store URL (examples: "469", "68179"; minLength: 1)
• 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: "SteamPackage")
• id integer required
• name string required
• image string nullable
• header_image string nullable
• small_logo string nullable
• page_content string nullable
• purchase_text string nullable
• controller_support string nullable
• release_date string nullable
• coming_soon boolean (default: false)
• price object nullable
  • @type string (default: "SteamPackagePrice")
  • currency string nullable
  • initial integer nullable
  • final integer nullable
  • discount_percent integer nullable
  • individual integer nullable
• platforms object nullable
  • @type string (default: "SteamPlatforms")
  • windows boolean (default: false)
  • mac boolean (default: false)
  • linux boolean (default: false)
• apps array (default: [])
  • @type string (default: "SteamPackageApp")
  • id integer required
  • name 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 — Package not found or unavailable in the requested storefront 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.