Scope
Lineage 2 API exposes cleaned, read-only JSON data for the Interlude chronicle. It is meant for tools, wikis, guides, price checkers, loot tables, and exploration. Raw data can be useful for server builders.
Covered
Section titled “Covered”- Interlude chronicle only
- Built from aCis Interlude client P746
- Items, NPCs, monsters, drops & spoil, quests, classes, hennas, locations, regions, armor sets
- Cleaned, cross-linked JSON data
- An OpenAPI spec
Not covered
Section titled “Not covered”- Other chronicles, for now
- Auth, accounts, comments, ratings, or moderation
- Runtime game-server behavior
- Full formula or damage simulation
Differences from L2Hub, PTS, L2Wiki, or other references usually come from source-data differences. Issues and PRs are welcome; see How to Contribute.
Public vs raw
Section titled “Public vs raw”The API exposes two layers:
- Public endpoints (
/api/interlude/npcs, …) are cleaned, normalized, deduplicated, and cross-linked. Use these by default. - Raw endpoints (
/api/interlude/raw/npcs, …) return raw parsed data as-is, without cleanup or enrichment.
Caching
Section titled “Caching”Successful responses are CDN-cacheable; data is immutable per deploy.
Cache-Control: public, max-age=300, s-maxage=86400, stale-while-revalidate=604800Error responses are never cached:
Cache-Control: no-storeCORS & browser usage
Section titled “CORS & browser usage”CORS is open (Access-Control-Allow-Origin: *) and no authentication is required, so the API works directly from a browser — no keys, no proxy.
Rate limits
Section titled “Rate limits”API routes are rate-limited by IP: 60 requests per 10 seconds. Normal browser usage won’t hit this, but high-volume scraping may receive 429 Too Many Requests.
Community project. Not affiliated with NCSoft.