Dungeon Fighter Online
DATA · DATA & ANALYTICS
Servers, character search, and a character’s stats and equipment.
Connecting Dungeon Fighter Online in practice
The Dungeon & Fighter API is Neople’s rather than Nexon’s global portal: api.neople.co.kr takes the key as an apikey query parameter or header and allows 1,000 requests a second per application. The catch is the character timeline, which searches at most a 90-day window and returns nothing at all if either startDate or endDate is missing.
Rate limits
- Per application: 1,000 requests per second, 60,000 per minute, 3,600,000 per hour.
- Row caps per endpoint, each defaulting to 10: auction search limit maximum 400, character search 200, character timeline 100, set-item search 100, item search 30, avatar market 50.
- Nexon Open API returns error code OPENAPI00007 with 429 Too Many Requests when a call limit is exceeded.
Worth knowing
- The timeline endpoint defaults to the last 30 days, accepts a window of at most 90 days, and fails the search outright if either startDate or endDate is omitted; no data exists before 2017-09-21.
- Timeline paging uses a next token, and when next is used the limit, code, startDate and endDate parameters stay fixed at the values from the first query, so a scan cannot be retuned midway.
- Two error codes are routine rather than exceptional: OPENAPI00009 "Data being prepared" and OPENAPI00010 "Service under maintenance" both return 400, so a retry-on-5xx policy never fires for either.
- The terms attach obligations to the data, not just the calls: Nexon requires cached data to be refreshed at least every 30 days and the phrase "Data based on NEXON Open API" to be displayed, Neople forbids charging users for access to the data, and a key left unused for a year or more can be restricted without notice.
Checked against Neople Open API common guide (2026-09-29), Dungeon & Fighter API docs (2026-09-29), Nexon Open API: using the API (2026-09-29), Neople Open API terms (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Dungeon Fighter Online behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.