ROXPEDIA API reference

Public, read-only endpoints for monster and item data. No API key is required.

Download OpenAPI JSON Open API URL

01 · GETTING STARTED

Connection

Base URL, response format, and supported languages.

Base URLhttps://roxpedia.com/api

AuthenticationNone

Response formatJSON

Languagesen · in · th · vn · kr · cn · tw

02 · ENDPOINTS

Endpoints

Use the list endpoint to find a record, then request the matching monster or item.

GET/api/monsters

Monster list

List monsters with pagination, search, filters, and EXP fields.

Parameterssearch, rp, bodily, page, limit

GET/api/monsters/{id}

Monster details

Return one monster with stats, skills, spawn data, and drops.

Parametersid, lang

GET/api/items/{slug}

Item details

Return one item with card data, drop sources, and crafting uses.

Parametersslug, lang

Method	Path	Purpose	Key parameters
GET	`/api/monsters`	Monster list	`search, rp, bodily, page, limit`
GET	`/api/monsters/{id}`	Monster details	`id, lang`
GET	`/api/items/{slug}`	Item details	`slug, lang`

03 · TRY IT

Request examples

Run any command below to test the public endpoint.

Shellcurl

curl "https://roxpedia.com/api/monsters?search=Poring&limit=5"

curl "https://roxpedia.com/api/monsters/10001?lang=en"

curl "https://roxpedia.com/api/items/blue-potion?lang=en"

04 · RESPONSE NOTES

Responses

Status codes, language fallback, and the machine-readable schema.

Status codes

Successful requests return 200. A missing monster or item returns 404 with a JSON error message.

Localization

Use en, in, th, vn, kr, cn, or tw, matching the TextAsset language codes. English is used when no language is supplied.

Item identifiers

Raw game ItemIDs stay internal. Public item URLs use slugs, and item responses do not include the raw identifier.

Machine-readable contract

Use the OpenAPI JSON document with Postman, API clients, validation tools, or code generators.