Versioning & migration
The DarkerDB API uses URL-prefix versioning. The current version is v2.
v1 → v2 changes
| v1 | v2 | Notes |
|---|---|---|
/v1/items | /v2/items | richer data, full filter set |
/v1/items/{id} | /v2/items/{id} | canonical id format (id.item.<slug> or upstream Id_Item_<Name>) |
/v1/population | /v2/population | unchanged shape |
/v1/population/history | /v2/population/history | requires from/to ISO 8601 |
/v1/market | /v2/market | new pagination cursor |
/v1/leaderboards | /v2/leaderboards | unchanged |
/v1/trades/chat | /v2/trades/chat | unchanged |
/v1/characters | /v2/characters | unchanged |
/v1/users/@me/keys | /v2/users/@me/keys | now reports tier and quota usage |
v1 sunset
The v1 API runs in parallel until DNS cutover, then is retired out-of-band. New integrations should target v2.
API keys do not survive cutover — legacy plaintext keys are unrecoverable. After cutover, regenerate via the dashboard.