Fandom hub

Fandom Page API

One Fandom article as clean JSON: readable text, wikitext, structured infoboxes, and who edited it last.

GET /v1/fandom/wikis/{wiki}/page

1 credit Failed requests are free

About this endpoint

GET /v1/fandom/wikis/{wiki}/page?title=… takes the title as it appears in the wiki URL (spaces and underscores are equivalent) and follows redirects, reporting the original title in redirectedFrom.

On found, data.page carries plainText with navigation, infoboxes, edit links and references stripped, so it reads like the article. It also carries the wikitext source (on by default; turn off with includeWikitext=false) and the rendered html when includeHtml=true. Infoboxes come back as infoboxes[] with a title, images and label/value fields (each with its group heading and template key), which is ideal for item, character and game data. Sections, categories, links, templates, images, external links, language links and the last editor, edit time and size round it out.

Fandom Page API FAQ

How do I name the wiki?

Use the subdomain: fortnite for fortnite.fandom.com, blox-fruits for blox-fruits.fandom.com. A full wiki URL also works. Add lang=de (or another code) for a language edition.

How do I get structured data like rarity or price?

Read data.page.infoboxes. Each field has a label (for example Rarity), the template key (rarity), its group heading, and the value as plain text.

How many credits does a page lookup cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth.

What does lookupStatus mean?

found means the page was returned. not_found means the wiki or page doesn't exist. HTTP 200 only means the request finished, so always branch on lookupStatus.

Can I get the HTML?

Yes, set includeHtml=true. HTML is off by default because article pages can be large; plainText and wikitext cover most uses.