Discover/Fandom API
live

Fandom APIaesthetics.fandom.com

Access 160+ design aesthetics from aesthetics.fandom.com. List all aesthetics, browse by category, and fetch infobox data including motifs, colours, and related styles.

Endpoint health
verified 5d ago
list_design_aesthetics
get_aesthetic_details
list_aesthetic_categories
list_aesthetics_by_category
4/4 passing latest checkself-healing
Endpoints
4
Updated
26d ago

What is the Fandom API?

The Aesthetics Wiki API exposes 4 endpoints covering the full catalog of design aesthetics from aesthetics.fandom.com, including roughly 163 entries in the Design Aesthetics category alone. Use get_aesthetic_details to retrieve structured infobox fields — decade of origin, key motifs, characteristic colours, predecessor and successor aesthetics — alongside a plain-text summary paragraph and the page's MediaWiki category memberships.

This call costs1 credit / call— charged only on success
Try it

No input parameters required.

api.parse.bot/scraper/1cf5559d-b4e9-48e2-9bc4-4e9d05e68f20/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/1cf5559d-b4e9-48e2-9bc4-4e9d05e68f20/list_design_aesthetics' \
  -H 'X-API-Key: $PARSE_API_KEY'
All endpoints · 4 totalmissing one? ·

Lists all design aesthetics from the Design Aesthetics category on the Aesthetics Wiki. Returns the complete set of aesthetics with their page IDs, titles, and wiki URLs. The category currently contains ~163 entries. A single call retrieves all entries (internally paginated against the wiki API with a hard cap of 20 iterations).

Input

No input parameters required.

Response
{
  "type": "object",
  "fields": {
    "total": "integer — number of aesthetics returned",
    "aesthetics": "array of aesthetic summary objects with page_id, title, and url"
  },
  "sample": {
    "data": {
      "total": 163,
      "aesthetics": [
        {
          "url": "https://aesthetics.fandom.com/wiki/2000s_Modern_Baroque",
          "title": "2000s Modern Baroque",
          "page_id": 53477
        },
        {
          "url": "https://aesthetics.fandom.com/wiki/8-Bit",
          "title": "8-Bit",
          "page_id": 36537
        },
        {
          "url": "https://aesthetics.fandom.com/wiki/Art_Deco",
          "title": "Art Deco",
          "page_id": 254
        }
      ]
    },
    "status": "success"
  }
}

About the Fandom API

What the API covers

The API mirrors the Aesthetics Wiki (aesthetics.fandom.com), a community-maintained reference for named visual and cultural aesthetic movements. list_design_aesthetics returns the complete set of entries in the Design Aesthetics category: each item carries a page_id, title, and url. The current count sits at approximately 163 aesthetics, retrieved in a single call with no pagination parameters required on the caller's side.

Detailed aesthetic data

get_aesthetic_details accepts an exact, case-sensitive title string — best obtained from the listing endpoint — and returns up to ten structured fields sourced from each page's infobox: key_motifs, key_values, key_colours, preceded_by, succeeded_by, plus a summary introductory paragraph and an array of categories the page belongs to. Fields not populated in the source infobox come back as null rather than empty strings, so null-checking is reliable for detecting genuinely absent data.

Category browsing

list_aesthetic_categories enumerates the ~22 subcategories under the wiki's "Aesthetics by Type" umbrella — covering groupings such as Internet Aesthetics, Music Genres, and Fashion Styles. Each object includes a category_key suitable for passing directly to list_aesthetics_by_category, which accepts both space and underscore variants of the category name and returns the same page_id, title, url shape as the design-aesthetics listing. Category membership is pulled live from the wiki, so new subcategories added by editors will appear in subsequent calls.

Reliability & maintenanceVerified

The Fandom API is a managed, monitored endpoint for aesthetics.fandom.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when aesthetics.fandom.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 aesthetics.fandom.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.

Last verified
5d ago
Latest check
4/4 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Building a searchable reference tool that maps aesthetic names to their characteristic colour palettes via key_colours
  • Tracing aesthetic lineage by following preceded_by and succeeded_by chains across multiple get_aesthetic_details calls
  • Populating a design-system tag taxonomy using categories membership returned per aesthetic page
  • Generating dataset snapshots of all ~163 design aesthetics with their core motifs for ML training or NLP classification
  • Filtering aesthetics by type (e.g. Fashion Styles vs. Internet Aesthetics) using list_aesthetics_by_category
  • Cross-referencing wiki page_id values with MediaWiki's public API for change-history or revision tracking
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 req/min

Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does aesthetics.fandom.com have an official developer API?+
Fandom wikis are built on MediaWiki and Fandom exposes a public REST API at https://www.fandom.com/api-docs. It covers generic wiki operations but does not model the Aesthetics Wiki's infobox fields (motifs, colours, predecessor/successor) as typed structured data. This API surfaces those fields directly.
What does `get_aesthetic_details` actually return for an aesthetic that has an incomplete infobox?+
Fields sourced from the infobox — key_motifs, key_values, key_colours, preceded_by, succeeded_by — return null when the wiki page does not populate them. The summary, url, title, page_id, and categories fields are always present as long as the page exists.
Does the API cover aesthetic pages outside the Design Aesthetics category, such as music- or internet-specific aesthetics?+
list_design_aesthetics is scoped to the Design Aesthetics category (~163 entries). Aesthetics in other type categories — Internet Aesthetics, Music Genres, Fashion Styles, and the remaining ~19 types — are accessible through list_aesthetics_by_category using the category names returned by list_aesthetic_categories. Full-text search across all wiki pages is not currently exposed. You can fork this API on Parse and revise it to add a search endpoint.
Does the API return images, gallery media, or the full wiki article body text for an aesthetic?+
Not currently. The API returns the introductory summary paragraph and structured infobox fields, but not full article wikitext, embedded images, or gallery sections. You can fork this API on Parse and revise it to add an endpoint that returns richer page content.
How fresh is the data, and does editing the wiki immediately affect what the API returns?+
The API reflects the current published state of each wiki page. Because aesthetics.fandom.com is a community wiki with ongoing edits, infobox values can change between calls. There is no built-in change-detection or webhook; callers needing stable snapshots should cache responses on their side.
Page content last updated . Spec covers 4 endpoints from aesthetics.fandom.com.
Related APIs in OtherSee all →
wikia.org API
Search and retrieve detailed information about characters, episodes, lore, and other content from Fandom wikis across thousands of fan communities. Browse wiki categories, look up specific pages, and access structured data about your favorite franchises all in one place.
wikia.com API
Extract structured data from Fandom (formerly Wikia) gaming wikis. Search pages, retrieve full page content, list category members, and convert wiki pages into organized guides with infoboxes, section breakdowns, and clean text.
Wikipedia API
Search Wikipedia and instantly access full article content on any topic, then explore related articles by browsing through Wikipedia categories. Retrieve article metadata, extracts, and navigate curated category trees to discover connected subjects.
smashingmagazine.com API
Access Smashing Magazine's library of articles, books, ebooks, newsletters, and events with powerful search and filtering capabilities. Browse by category, discover related content, explore author profiles, and stay updated with the latest design and web development resources.
textures.com API
Search and browse millions of textures by category or keyword to find high-resolution texture maps with detailed pricing and specifications. Discover the latest content additions, explore free samples, and access complete metadata including available resolutions and texture maps for your projects.
valorant.fandom.com API
Access data from valorant.fandom.com.
elements.envato.com API
Search and browse millions of creative assets from Envato Elements, including stock photos, videos, music, fonts, and templates across all categories. Get detailed information about specific items, pricing plans, and discover new content through keyword search and category browsing.
eldenring.wiki.fextralife.com API
Search and retrieve structured Elden Ring game information from the Fextralife Wiki, including weapons, enemies, locations, and lore. Access full article content with hierarchical sections, tables, and images, or search the complete article catalog by keyword.