Games & Comics — entry 030 of 75
Genshin Impact
genshin.dev is a fan-made, keyless static-data API for Genshin Impact covering characters, weapons, artifacts, elements, and related in-game entities, with an always-current instance mirrored at genshin.jmp.blue. Per-type list, detail, and image endpoints (e.g. /characters, /characters/albedo, /characters/albedo/card) support an optional lang parameter for localized responses; it only mirrors static reference data and never touches a player's live game account.
genshin.dev's live API is served from a separate host, genshin.jmp.blue, and its list endpoints return bare arrays of slug strings — not objects — a shape no other quickstarted API in this atlas covers. A live GET this run against /characters returned a genuine 909 B array at HTTP 200, content-type: application/json; charset=utf-8.
GreatAPIs Score
Auth quickstart
- No API key, signup, or credit card required — the live GET above returned real character slugs with no auth header of any kind attached. CORS echoes the caller's
Origin, and Helmet-style headers (x-content-type-options,x-frame-options) are present, so direct browser use works too.
Your key is stored only in this browser (localStorage) and sent directly to the API — never to greatapis.
List character slugs, then fetch one in full
GEThttps://genshin.jmp.blue/characters
["albedo","alhaitham","aloy","amber","arataki-itto","arlecchino","ayaka","ayato","baizhu","barbara"]
The list is a bare array of slug strings, not objects — there is no name, element, or rarity here. To get an actual character object you fetch the slug: a live GET this run against /characters/albedo returned a full 7,703 B character object at HTTP 200 (same content type).
Try it
Developer reference
https://genshin.jmp.blue- GET/characters
- GET/characters/{name}
- GET/weapons
- GET/elements
Gotchas & limits
- Every list-type endpoint returns bare slug strings, never objects. Confirmed live this run on both
/characters(909 B, shown above) and/weapons(3,538 B, opening["a-thousand-floating-dreams","akuoumaru","alley-hunter",...]) — code expecting{name, ...}objects from a list endpoint will get plain strings instead on every resource type. - The API is self-describing at its root. A live GET this run against
/(bare host, no path) returned 200, 120 B:{"types":["artifacts","boss","characters","consumables","domains","elements","enemies","materials","nations","weapons"]}— that's the full list of valid first-path-segment resource types, fetched live rather than guessed. - A bad slug names the language in its error message, hinting at an undocumented
langdimension. A live GET this run against/characters/nosuchcharreturned HTTP 404, 66 B:{"error":"Entity characters/nosuchchar for language en not found"}. - The entry's
urlin apis.json (https://genshin.dev) is a documentation SPA on a different host from the API — confirmed live this run, 200,text/html.baseUrl(https://genshin.jmp.blue) is the actual data host; the two are not interchangeable.