Overview

Version
v2.1.3
Host
https://api.qa.darkerdb.com

The DarkerDB API serves Dark and Darker game data as plain JSON: items, monsters, maps, quests, loot, market prices, and more. Every response is wrapped in a standard envelope:

GET
Parameter flagsRequired, optional, and global options are color coded. Global options behave consistently across endpoints.

Game data vs live data

The API serves two families that behave differently. Know which one you're reading:

Game data

The static catalog pulled from the game's design files: items, monsters, maps, quests, loot, and more. It's patch-versioned and cached, so it only changes when a new patch lands.

Scopedarkerdb.data
Live data

Observations captured from the running game: market listings, trades, population, and leaderboards. It updates continuously and isn't patch-time-travelable. Live endpoints are throttled tighter.

Scopedarkerdb.live

Authentication

Most reads need an API key. Sign in with Discord, then mint one on the API keys dashboard. Send it in the X-API-Key header:

bash
curl https://api.darkerdb.com/v2/items \
  -H "X-API-Key: your-api-key"

Each key carries one or more scopes that gate what it can read and set its own rate limit. A few keyless routes (icons, model and map images, the health probe) stay open. See Authentication for scopes and rate limits.

Released clients should also pin an API contract. Omitting X-API-Version follows the latest response shape.

Support

Built something with the API, hit a snag, or want an endpoint that isn't here yet? Join the discussion in our Discord.