Data Status
How Goblin Ledger sources and stores auction house data
Snapshots are saved via POST /api/snapshots (service role) and read via GET /api/snapshots/history (publishable key on the server). The service role key never reaches the browser.
- Realms
- 7
- Items
- 12
- Snapshots
- 1
Goblin Ledger calls Blizzard's Battle.net API server-side when BLIZZARD_CLIENT_ID and BLIZZARD_CLIENT_SECRET are set. Retail realms use the direct /auctions endpoint. Classic realms try the auction house index first, then fall back to the direct endpoint.
Classic Era (dynamic-classic1x-us) and Burning Crusade Anniversary (dynamic-classic-us) auction house endpoints frequently return 404 Not Found from Blizzard. This is a Blizzard-side API limitation, not a Goblin Ledger bug.
When both the index and direct auction endpoints fail, item pages show a warning and fall back to sample prices so the UI remains useful while Classic AH data is unavailable.
Sample data includes realistic mock prices, 7-day history charts, and realm-specific snapshots for Classic Era and TBC Anniversary realms. Pages label the source as Sample Data when Blizzard live data is not shown.
Watchlist and search features work with sample data so you can still track items locally without a login.