/epicgames/sellers

POST /api/epicgames/sellers

Price: 10 credits

Get an Epic Games Store publisher or developer with the list of their catalog games

How to use it

Get an Epic Games Store seller (publisher or developer) together with the games they sell. Provide the seller's display name exactly as it appears in a game's seller block (for example 'CD PROJEKT RED' or 'Annapurna Interactive'). Returns the seller name and id plus their catalog games, each with title, description, release date, offer type, categories and tags, key images, and price with original and discounted amounts, currency, and discount percentage for the selected country.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• seller string required — Publisher or developer as it appears in a game's seller block — its display name or seller id (examples: "CD PROJEKT RED", "Annapurna Interactive", "Devolver Digital, Inc."; minLength: 1)
• count integer required — Max number of games to return (min: 1)
• country string — Store country, drives price and currency (default: "US"; one of: "US", "GB", "CA", "AU", "DE", "FR", "IT", "ES", "NL", "BR", "MX", "IN", "JP", "KR", "TR", "RU", "PL")
• locale string — Content language (default: "en-US"; one of: "en-US", "en-GB", "de-DE", "fr-FR", "it-IT", "es-ES", "nl-NL", "pt-BR", "es-MX", "ja", "ko", "tr", "ru", "pl")

Response

• @type string (default: "EpicgamesSellerProfile")
• id string nullable
• name string required
• game_count integer (default: 0)
• games array (default: [])
  • @type string (default: "EpicgamesGame")
  • id string required
  • namespace string required
  • alias string nullable
  • description string nullable
  • long_description string nullable
  • offer_type string nullable
  • release_date string nullable
  • effective_date string nullable
  • seller object nullable
    • @type string (default: "EpicgamesSeller")
    • id string nullable
    • name string required
  • developer string nullable
  • publisher string nullable
  • image string nullable
  • images array (default: [])
    • @type string (default: "EpicgamesImage")
    • image_type string required
    • url string required
  • categories array (default: [])
  • tags array (default: [])
    • @type string (default: "EpicgamesTag")
    • id string nullable
    • name string required
    • group_name string nullable
  • price object nullable
    • @type string (default: "EpicgamesPrice")
    • original_price number nullable
    • discount_price number nullable
    • currency_code string nullable
    • discount number nullable
    • discount_percent integer nullable
    • original_price_display string nullable
    • discount_price_display string nullable
  • 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 — Seller 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.