Kinguin Key Search

Collect public kinguin key search data into a clean dataset for price research, catalog analysis and reporting. No browser session or cookies are needed.

What you get

• One row per unique product or result, with an image first when available.
• Readable summary fields plus sourceData with all nonempty commerce fields returned for that result.
• Available image arrays, nested attributes and price blocks are kept without extra per-item enrichment requests.
• Automatic pagination until the requested result count or the available results are exhausted.
• JSON, CSV and Excel export through Apify datasets. Nested data is most complete in JSON.

Start a run

Use the prefilled example, change the search or identifiers, then set Maximum results.

{
  "query": "witcher",
  "maxItems": 30
}

Inputs

• Search phrase: Search words. For example witcher.
• Maximum results: Stop after this many unique results. Pagination is automatic.

Output

image, id, title and the available price/rating fields give a compact view. sourceData keeps the full commerce details rather than flattening away arrays. Missing fields are omitted instead of filled with empty columns. Dates are formatted DD-MM-YYYY; any time suffix is retained.

Important details

Includes activation regions, platforms, product attributes and raw price fields. Raw price units/currency are not normalized or guaranteed, and large sentinel values may mean no offer. Do not treat these fields as a final checkout quote. Account/access offers may be mixed with keys; inspect product names and attributes.

Rows contain public commerce data only. Reviewer profiles, seller personal data and backend service links are removed. Product descriptions and review text are returned as text, not rendered HTML. Respect the source site's terms, content rights and applicable law. This actor is independent and is not endorsed by the source marketplace.

Results and billing

One result event is charged per saved unique row, using the rate shown on this listing. Duplicate rows are not charged again within the same run. No charge event is emitted for invalid input or empty results.

Empty results and errors

Invalid input or unavailable identifiers finish successfully with an explanation and a working example in Run status. The same record tells you how many pages and results were saved. A partial run keeps its results and reports a warning. A complete service outage can fail the run so it is not mistaken for an empty search. Public sources can change or limit access; no speed or long-term availability guarantee is made.