Gamepedia APIgamepedia.com ↗
Access page content, search, categories, images, and metadata from any Fandom/Gamepedia wiki via 19 endpoints. Target any game wiki by subdomain.
What is the Gamepedia API?
This API exposes 19 endpoints covering content, search, navigation, and media across any Fandom/Gamepedia wiki. Use search_wiki to find pages by keyword with snippet previews, get_wiki_page_html to retrieve fully rendered article HTML with sections and categories, or get_image_info to pull direct download URLs and dimensions for any wiki image file. A single subdomain parameter switches the target wiki — from minecraft to leagueoflegends to zelda.
curl -X GET 'https://api.parse.bot/scraper/8e808513-8d56-405d-9ad6-94360a42ad04/search_wiki?wiki=minecraft&limit=5&query=diamond&offset=0&namespace=0&subdomain=minecraft' \ -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 gamepedia-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.
"""
Fandom Wiki API - Usage Example
Get your API key from: https://parse.bot/settings
"""
from parse_apis.fandom_wiki_api import Fandom, Namespace, Subdomain, PageNotFound
client = Fandom()
# Search for pages on the Minecraft wiki — limit caps total items fetched
for result in client.pages.search(query="diamond", subdomain=Subdomain.MINECRAFT, limit=3):
print(result.title, result.pageid, result.timestamp)
# List top/trending articles on the wiki
top = client.pages.top(subdomain=Subdomain.MINECRAFT, limit=3).first()
if top:
print(f"Top article: {top.title} (id={top.id}, url={top.url})")
# Construct a category by name and list its members
blocks = client.category("Blocks")
for page in blocks.members(subdomain=Subdomain.MINECRAFT, limit=3):
print(f" Block: {page.title} (pageid={page.pageid})")
# List pages in a specific namespace using the Namespace enum
for page in client.pages.list_by_namespace(namespace=Namespace._14, subdomain=Subdomain.MINECRAFT, limit=3):
print(f" Category page: {page.title}")
# Autocomplete/suggest page titles
suggestions = client.pages.opensearch(query="creeper", subdomain=Subdomain.MINECRAFT)
print(f"Opensearch query: {suggestions.query}")
# Typed error handling: catch PageNotFound for a missing page
try:
for result in client.pages.search(query="xyznonexistent999", limit=1):
print(result.title)
except PageNotFound as exc:
print(f"Page not found: {exc}")
# Recent changes feed
for change in client.recentchanges.list(subdomain=Subdomain.MINECRAFT, limit=3):
print(f" [{change.type}] {change.title} by {change.user} at {change.timestamp}")
print("exercised: pages.search / pages.top / category.members / pages.list_by_namespace / pages.opensearch / recentchanges.list")
Full-text search over a Fandom wiki's pages. Returns page titles, IDs, sizes, timestamps, and text snippets. Paginates via integer offset (sroffset from previous response). Each result includes namespace, title, page ID, byte size, snippet, and last-edit timestamp.
| Param | Type | Description |
|---|---|---|
| limit | integer | Max results to return |
| queryrequired | string | Search query string |
| offset | integer | Offset for pagination (from sroffset in previous response) |
| namespace | string | Namespace ID to search in (e.g., '0' for Main, '14' for Category) |
| subdomain | string | Wiki subdomain (e.g., 'minecraft', 'zelda', 'leagueoflegends') |
{
"type": "object",
"fields": {
"results": "array of search results with ns, title, pageid, size, snippet, timestamp per result",
"sroffset": "integer offset for next page, null if no more results"
},
"sample": {
"data": {
"results": [
{
"ns": 0,
"size": 15655,
"title": "Diamond",
"pageid": 31051,
"snippet": "",
"timestamp": "2025-12-14T05:52:54Z",
"titlesnippet": ""
}
],
"sroffset": 10
},
"status": "success"
}
}About the Gamepedia API
Page Content and Formats
Three endpoints cover the same article in different formats. get_wiki_page_html returns the rendered text field (full HTML), plus sections, images, links, and categories — useful when you need display-ready content. get_wiki_page_wikitext returns the raw wikitext source via revisions, which preserves infobox templates and structured markup. get_wiki_page_summary accepts a comma-separated list of numeric article ids and returns title, url, abstract, and thumbnail for each — practical for lightweight card-style displays without fetching full HTML.
Search and Discovery
search_wiki accepts a query string and optional namespace and limit params, returning pageid, title, size, snippet, and timestamp per result. Pagination uses continue.sroffset from each response. opensearch_wiki returns a four-element positional array — query string, matching titles, descriptions, and full URLs — suited for autocomplete UIs. get_top_articles returns the most-viewed articles on a wiki as an array with id, title, url, and ns fields.
Categories and Navigation
list_category_members lists every page in a named category, paginating via continue.cmcontinue. list_all_categories enumerates all categories on a wiki with optional prefix filtering. get_wiki_page_categories retrieves every category a single page belongs to. list_pages_by_namespace lets you walk all pages in a given namespace (Main=0, Template=10, File=6, etc.) with apcontinue-based pagination. get_page_links and get_backlinks expose the internal link graph in both directions.
Images, Metadata, and Site Info
get_image_info returns url, size, width, height, mime, timestamp, and user for any named file. get_page_images lists all filenames embedded on a page. get_wiki_page_metadata includes thumbnail, pageimage, pageprops, fullurl, and canonicalurl — the pageprops field often carries infobox identifiers. get_wiki_site_info gives aggregate statistics: total pages, articles, edits, images, and users alongside namespace definitions. get_recent_changes streams edit activity with type, user, timestamp, and comment per change.
The Gamepedia API is a managed, monitored endpoint for gamepedia.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when gamepedia.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 gamepedia.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 Minecraft item database by iterating
list_category_membersfor item categories and fetching wikitext infoboxes viaget_wiki_page_wikitext - Power an in-game tooltip overlay by calling
get_wiki_page_summarywith article IDs to retrieveabstractandthumbnailfields - Track wiki edit activity on a League of Legends wiki by polling
get_recent_changesforuser,timestamp, andcommentfields - Construct a cross-wiki search UI using
search_wikiwith snippet previews andopensearch_wikifor live title autocomplete - Resolve user-typed redirects (e.g. alternate item spellings) to canonical page titles using
resolve_redirect - Audit image assets on a wiki page by combining
get_page_imagesto list filenames withget_image_infofor direct URLs and dimensions - Map the internal link graph of a game wiki by walking
get_page_linksandget_backlinksfor a seed article
| 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/Gamepedia have an official developer API?+
https://{wiki}.fandom.com/api.php and a Fandom-specific extension API. Documentation is available at https://www.mediawiki.org/wiki/API:Main_page and Fandom's own developer docs. The Parse API consolidates common operations across wikis into a single interface with a uniform subdomain parameter.How does the `subdomain` parameter work, and what happens if I omit it?+
subdomain string such as minecraft, zelda, or leagueoflegends, which routes the request to that specific Fandom wiki (e.g. minecraft.fandom.com). If you omit it, the API targets a default wiki. You should always specify it explicitly when working with game-specific content.How does pagination work across list endpoints?+
search_wiki, list_category_members, list_all_categories, list_pages_by_namespace, get_backlinks, and get_recent_changes — include a continue object in the response. Pass the token from that object (e.g. sroffset, cmcontinue, apcontinue) as the continue input on your next call to retrieve the next page. Each token is specific to its endpoint and cannot be mixed across different endpoints.Can I retrieve wiki user profiles, talk-page discussions, or edit history for a specific page?+
Does `get_wiki_page_metadata` return full infobox field values?+
pageprops field in the metadata response carries infobox-related identifiers and properties as set by the wiki's templates, but it does not return fully parsed key-value infobox tables. For complete infobox data, use get_wiki_page_wikitext and parse the raw template markup from the revisions field. You can fork this API on Parse and add a dedicated infobox-parsing endpoint if you need structured output.