Lineage 2 API
A public, read-only HTTP API for Lineage 2 Interlude game data.
Base URL
Section titled “Base URL”https://l2api.dev/api/interludeEvery route is scoped by chronicle. Today the only supported chronicle is interlude.
Main resources
Section titled “Main resources”| Resource | URL | What’s there |
|---|---|---|
| items | /api/interlude/items?limit=10 | Weapons, armor, consumables, quest items, spellbooks, recipes |
| npcs | /api/interlude/npcs?limit=10 | Non-player characters: merchants, guards, quest givers |
| monsters | /api/interlude/monsters?limit=10 | Combat mobs: regular enemies, bosses, raid bosses |
| quests | /api/interlude/quests | Quest catalog, objectives, rewards |
| classes | /api/interlude/classes | Player classes and skill progression |
| hennas | /api/interlude/hennas | Dye and symbol items |
| armor-sets | /api/interlude/armor-sets | Armor set pieces and set bonuses |
| locations | /api/interlude/locations | Hunting zones and map locations |
items, npcs, and monsters are paginated and searchable (?q=wolf, ?limit=10, see Query parameters). quests, classes, hennas, armor-sets, and locations are small catalogs returned in full in one response. URLs are relative to the base https://l2api.dev.
Try it
Section titled “Try it”Pick an example, then Try it to see the live JSON, or Copy the URL.
Sample response
Response shape
Section titled “Response shape”// single resource{ "data": { } }
// list resource{ "data": [ ], "meta": { } }Always read from data. See Endpoints for query parameters, pagination and errors, and Code examples for ready-to-run fetch snippets.
No authentication
Section titled “No authentication”No API keys. CORS is enabled, so browser apps can call the API directly.