Wikia APIwikia.com ↗
Search Fandom wiki pages, retrieve full content with infoboxes, list category members, and convert wiki pages into structured guides via 4 endpoints.
What is the Wikia API?
The Fandom (Wikia) API exposes 4 endpoints for extracting structured data from any Fandom wiki — covering page search, full-text retrieval, category membership, and guide generation. The get_page endpoint returns infobox key-value pairs, section headings, category memberships, and clean stripped text for any exact page title. You can target any wiki by passing its slug — such as eldenring, cyberpunk2077, or zelda — making it straightforward to pull game data across thousands of Fandom communities.
curl -X GET 'https://api.parse.bot/scraper/96873755-3d4e-4369-a5eb-881c2b8750c8/search?wiki=eldenring&limit=5&query=Malenia' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace wikia-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Fandom Gaming Wiki SDK — search, browse, and extract structured guides."""
from parse_apis.fandom_gaming_wiki_api import Fandom, PageNotFound
client = Fandom()
# Search the Elden Ring wiki for boss-related pages.
elden = client.wiki("eldenring")
for result in elden.search(query="Malenia", limit=3):
print(result.title, result.size, result.wordcount)
# Drill into the first search result to get the full page.
hit = elden.search(query="Radahn", limit=1).first()
if hit:
page = hit.details()
print(page.title, len(page.categories), page.clean_text[:120])
# Fetch a page directly and convert it to a structured guide.
page = client.pages.get(title="White Mask Varré")
guide = page.guide()
print(guide.title, guide.summary[:80] if guide.summary else "(no summary)")
for section_name in list(guide.sections)[:3]:
print(f" section: {section_name}")
# Browse a category to list member pages.
for member in elden.category(category="Bosses", limit=5):
print(member.title, member.pageid)
# Typed error handling when a page title doesn't exist.
try:
client.pages.get(title="Nonexistent Page XYZ 9999")
except PageNotFound as exc:
print(f"not found: {exc.title}")
print("exercised: wiki.search / search_result.details / pages.get / page.guide / wiki.category / PageNotFound")
Full-text search across a Fandom wiki's pages. Returns matching page titles with metadata (page ID, byte size, word count, last-modified timestamp). Results are server-ranked by relevance. Each result carries enough metadata to decide whether to fetch the full page via get_page or get_guide.
| Param | Type | Description |
|---|---|---|
| wiki | string | The wiki slug identifying which Fandom wiki to search (e.g., 'eldenring', 'cyberpunk2077', 'zelda'). |
| limit | integer | Maximum number of search results to return (1-50). |
| queryrequired | string | Search keyword or phrase to match against page titles and content. |
{
"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 API
Search and Page Retrieval
The search endpoint accepts a query string plus an optional wiki slug and limit (1–50), returning an array of result objects that each include pageid, title, size, wordcount, snippet, and timestamp. Results are ranked by the wiki's own relevance scoring. This is the right starting point when you don't know exact page titles — use the pageid or title from results to feed into get_page.
The get_page endpoint takes an exact, case-sensitive title and returns the full page: an infobox object of key-value pairs, a sections array with title, level, and anchor per section, a categories array of strings, and clean_text with all HTML removed. Because titles must match exactly, running a search call first is the reliable way to confirm the right title string before calling get_page.
Guides and Category Browsing
The get_guide endpoint accepts the same wiki and title inputs but restructures the page differently: it returns a summary from the first paragraph, the infobox object, and a sections object whose keys are section header names and whose values are arrays of typed content items — each item carries a type field (text, list, or table) alongside its content. This is purpose-built for rendering game walkthroughs, boss breakdowns, or item guides without having to parse clean_text yourself.
The get_category endpoint lists all pages belonging to a named category in the target wiki, returning up to 100 member objects each with pageid, ns, and title. The Category: prefix is appended automatically if omitted. Category names can be discovered from the categories array returned by get_page, so these two endpoints compose naturally for bulk page enumeration within a topic area.
The Wikia API is a managed, monitored endpoint for wikia.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when wikia.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official wikia.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a searchable boss database for an Elden Ring fan app using
searchandget_pageinfobox data - Generate structured quest walkthroughs by converting wiki pages to typed section content via
get_guide - Enumerate all pages in a 'Characters' or 'Weapons' category with
get_categoryto seed a game companion database - Extract clean lore text from any Fandom wiki page using the
clean_textfield fromget_page - Power autocomplete or page-lookup features using
searchresult snippets and timestamps - Aggregate infobox stats (attack, defense, drop rate) across item pages retrieved via category member titles
- Sync a local wiki mirror by tracking
timestampfields fromsearchresults to detect recently edited pages
| 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 | 100 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?+
https://{wikislug}.fandom.com/api.php, which exposes standard MediaWiki query actions. It is publicly documented but rate-limited, inconsistently structured across wikis, and returns raw wikitext rather than clean structured data. This API wraps that data into consistent, pre-parsed response shapes.What does `get_guide` return that `get_page` doesn't?+
infobox data and page content, but get_guide restructures content into a sections object where each entry is an array of typed items (text, list, or table). It also extracts a summary from the first paragraph. get_page instead returns a flat clean_text string and a sections array of heading metadata (title, level, anchor) without sectioned content items. Use get_guide when you need content pre-organized by section; use get_page when you need the full raw text or heading structure.How many category members does `get_category` return, and can I paginate?+
Can I retrieve revision history or user contribution data for a wiki page?+
Does title matching in `get_page` handle redirects or alternate spellings?+
title parameter is case-sensitive and must match the canonical page title exactly, including punctuation. Redirects are not automatically resolved — if you pass a redirect page title, you receive that redirect page's content rather than the destination. Use the search endpoint first to find the canonical title before calling get_page.