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!
Quests
Everything about a quest in one response — title, description, objectives, and rewards. Both list and single-quest endpoints inline the resolved objective rows and reward entries; you never need a follow-up fetch. Always reflects the current patch.
title is always non-null. Quests the game ships no locale string for receive a readable fallback derived from the id — "Alchemist 31" for id.quest.alchemist_31. Use the name filter to search by either the localized title or the canonical id.
Quest contents, rewards, and quest chapters are no longer separate public endpoints. Their data is served through this consolidated /quests response so consumers don't have to chase references across endpoints.
GET /v2/quests
GET /v2/quests/{id}
The single-quest GET returns the same per-row shape as the list endpoint. Each objectives[] entry carries content_type, content_count, target_archetype (which you can pivot to /items or /monsters via ?archetype=…) and a list of dungeon_tags when the objective is location-gated.
Each rewards[*].entries[] entry has a type + count plus a type-specific reference field. Types: item (with item_id), experience, adventure_points, random (with random_reward_id), affinity, item_skin, character_skin, armor_skin, nameplate_skin, action, emote, stash, none. The slugs are mechanically derived from the game's EDCRewardType::* enum, so new types in future patches appear automatically.