Nintendo eShop search · Nintendo eShop API

GET https://api.api.sh/nintendo/v1/search

1 credit / call media & music try it in the playground →

Games (or DLC) in Nintendo's European catalogue by words, system, genre, publisher, price range (EUR), sale and demo, with every sort: eShop ids, systems, publisher, release date, genres, age rating, players, play modes, languages, size, price and discount.

Every response includes credits_used: the credits this call cost.

Parameters

name	type	description
`q`	string	Search words (empty: all games). Example: `zelda`
`system`	string	System, e.g. Nintendo Switch, Nintendo Switch 2.
`genre`	string	Genre, e.g. Action, Adventure, RPG, Puzzle, Platformer.
`publisher`	string	Publisher name.
`on_sale`	true \| false	Only games on sale.
`demo`	true \| false	Only games with a demo.
`price_min`	number	Minimum price (EUR).
`price_max`	number	Maximum price (EUR).
`type`	game \| dlc \| all	What (default game).
`sort`	relevance \| popular \| newest \| oldest \| price_asc \| price_desc \| title \| discount	Order (default relevance with q, else popular).
`locale`	en \| de \| fr \| es \| it \| nl \| pt \| ru	Catalogue language (default en).
`page`	integer	Page number (default 1). Pass `next_page` back; null on the last page.
`limit`	integer	Results per page (1-100, default 24).

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/nintendo/v1/search?q=zelda" \
  -H "x-api-key: $APISH_KEY"

import os, requests

res = requests.get(
    "https://api.api.sh/nintendo/v1/search",
    params={"q": "zelda"},
    headers={"x-api-key": os.environ["APISH_KEY"]},
    timeout=120,
)
res.raise_for_status()
data = res.json()

const url = new URL("https://api.api.sh/nintendo/v1/search");
url.searchParams.set("q", "zelda");

const res = await fetch(url, { headers: { "x-api-key": process.env.APISH_KEY } });
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json();

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.