Explore the
DarkerDB API documentation, your gateway to harnessing Dark and Darker game data. Use our APIs to track in-game market trends, analyze live player stats, and access detailed item data, including stats, descriptions, and market data. Download game assets like item icons to enhance your apps or generate interactive tooltips. Feel free to get in touch with us in our Discord for support or to request new features or data!
Modules
Dungeon modules — the per-tile primitives the runtime drops into layout slots at dungeon-generation time. Each row carries a 512×512 map_image texture extracted from the game's .pak files every patch.
module_type groups tiles by dungeon family (crypt, goblin_cave, ice_cavern, ruins, inferno, …).
GET /v2/modules
GET /v2/modules/{id}
Returns the module row: name, module_type, size_x/size_y (grid footprint), and is_edge_only.
GET /v2/modules/{id}/image
Spawns
Per-tile placement of every spawn point — monsters, loot drops, props — with tile-relativeposition and rotation. position.x/y/z are Unreal world units (1 uu ≈ 1 cm) measured from the tile origin; world position is tile_origin + position where tile_origin comes from the layout slot at dungeon-generation time. rotation carries pitch/yaw/roll.
The spawn sub-object inlines the matching spawner definition (type / monster_id) so a single request gives you everything to render. Variants: a (Adventure), d (Duo), hr_d (HighRoller Duo), sr_d (Squires-to-Riches Duo), b (alternate). The _S "Server" variants on disk carry only collision geometry and are excluded.