wikia.com APIwikia.com ↗
Access Fandom wiki data via 4 endpoints: search pages, retrieve full content, list categories, and extract structured gaming guides with infoboxes and sections.
curl -X GET 'https://api.parse.bot/scraper/96873755-3d4e-4369-a5eb-881c2b8750c8/search?wiki=eldenring&limit=10&query=Malenia' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for pages within a specific gaming wiki on Fandom. Returns matching page titles with metadata such as page ID, size, word count, and last modified timestamp.
| Param | Type | Description |
|---|---|---|
| wiki | string | The wiki slug (e.g., 'eldenring', 'cyberpunk2077'). |
| limit | integer | Maximum number of search results to return. |
| queryrequired | string | Search keyword (e.g., 'Malenia', 'Bleed Build'). |
{
"type": "object",
"fields": {
"wiki": "string — the wiki slug queried",
"results": "array of search result objects, each containing ns, title, pageid, size, wordcount, snippet, and timestamp"
},
"sample": {
"data": {
"wiki": "eldenring",
"results": [
{
"ns": 0,
"size": 27340,
"title": "Malenia, Blade of Miquella",
"pageid": 427,
"snippet": "",
"timestamp": "2026-04-19T22:37:47Z",
"wordcount": 4014
}
]
},
"status": "success"
}
}About the wikia.com API
The Fandom (Wikia) API provides 4 endpoints for extracting structured data from any Fandom gaming wiki. Use get_guide to convert a wiki page into a structured guide with infobox fields, a summary, and typed content sections — or use search to find pages by keyword across a specific wiki slug, returning page IDs, word counts, and last-modified timestamps.
Endpoints and Data Coverage
The search endpoint queries a specific Fandom wiki by wiki slug (e.g., eldenring, cyberpunk2077) and query string, returning an array of result objects. Each result includes pageid, title, size, wordcount, snippet, and timestamp. The optional limit parameter controls how many results come back.
The get_page endpoint retrieves full page content for a given title. The response includes an infobox object with key-value pairs pulled from the page's info table (fields like Type, Location, Class), a sections array with title, level, and anchor for each heading, a categories array of category name strings, and clean_text — the full page text with HTML stripped.
Guide and Category Endpoints
get_guide parses a page into a structured gaming guide. The response includes the same infobox and a summary extracted from the first paragraph, plus a sections object where each key is a section header (e.g., "Overview", "Location", "Events in Game") and each value is an array of typed content items — text, list, or table. This makes it straightforward to render or index a guide without further parsing.
get_category lists up to 100 members of a given wiki category. Pass a category name (the Category: prefix is added automatically) along with a wiki slug, and the response returns a members array with pageid, ns, and title for each page. This is useful for enumerating all bosses, quests, items, or other categorized content within a wiki.
- Build a boss reference tool by calling
get_guidefor each entry in a wiki's 'Bosses' category, surfacing infobox stats and strategy sections. - Index Fandom wiki content for a game companion app using
searchto find pages by character or item name. - Populate a game database with structured page data — types, locations, and categories — via
get_pagefor any wiki slug. - Enumerate all quests or items in a game by listing a category with
get_categoryand then fetching each page. - Extract clean, HTML-free page text from
clean_textfor use in a semantic search index or LLM context. - Render structured walkthroughs by mapping
get_guidesections into typed blocks (text, list, table) in a documentation site. - Compare infobox fields across multiple wiki pages (e.g., boss health values) by batching
get_pagerequests.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Fandom have an official developer API?+
{wiki}.fandom.com/api.php, which remains accessible on many wikis but is undocumented, inconsistently available across wikis, and returns raw MediaWiki markup rather than structured content. This Parse API returns cleaned, structured data with infoboxes, typed sections, and categories already parsed.What does `get_guide` return differently from `get_page`?+
get_page returns a flat clean_text string, a sections array with heading metadata (title, level, anchor), and raw categories. get_guide goes further: it structures the page body into a sections object keyed by header name, where each value is an array of typed content items — text, list, or table. It also extracts a summary from the first paragraph. Use get_guide when you need renderable, typed content blocks; use get_page when you need raw text or heading structure.Does `get_category` paginate beyond 100 members?+
offset or continue parameter exposed. You can fork this API on Parse and revise it to add pagination support if you need to enumerate categories with more than 100 members.Does the API cover non-gaming Fandom wikis (TV shows, movies, books)?+
wiki slug, so any Fandom wiki is technically reachable. However, the get_guide endpoint is designed around gaming-page structures (infoboxes with fields like Type, Location, Class; sections like Overview and Walkthrough). Pages from non-gaming wikis will still return data, but section parsing and infobox extraction may be less consistent. You can fork this API on Parse and revise it to tune parsing for entertainment or media wikis.