Discover/Fandom API
live

Fandom APIpiggy.fandom.com

Retrieve all Piggy (Roblox) character skins from the fandom wiki, including names, thumbnail images, book grouping, and subcategory via a single endpoint.

This API takes change requests — .
Endpoint health
verified 49m ago
get_skins
1/1 passing latest checkself-healing
Endpoints
1
Updated
1mo ago

What is the Fandom API?

The Piggy Fandom Skins API provides structured data on every playable character skin listed on piggy.fandom.com, covering 4 response fields per skin across all book groupings and subcategory tabs. The single get_skins endpoint returns a complete list of skins with names, thumbnail image URLs, book assignments (such as Book 1, Book 2, or PIGGY: Hunt Exclusive), and subcategory labels — no wiki browsing required.

Try it
Maximum number of skins to return.
Thumbnail image width in pixels for scaling.
api.parse.bot/scraper/1e2878da-cc05-4735-a4e7-e46b8816bc53/<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/1e2878da-cc05-4735-a4e7-e46b8816bc53/get_skins?limit=20&thumb_size=200' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

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 piggy-fandom-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: Piggy Wiki Skins API — browse and filter the skin collection."""
from parse_apis.piggy_wiki_skins_api import PiggyWiki, SkinNotFound

client = PiggyWiki()

# List skins with a custom thumbnail size, capped to 5 items
for skin in client.skins.list(thumb_size=150, limit=5):
    print(skin.name, skin.book, skin.subcategory)

# Drill into the first skin from the full collection
skin = client.skins.list(limit=1).first()
if skin:
    print(f"First skin: {skin.name} — Book: {skin.book}, Image: {skin.image_url}")

# Typed error handling around a list call
try:
    for s in client.skins.list(thumb_size=200, limit=3):
        print(s.name, s.image_url)
except SkinNotFound as exc:
    print(f"Skin not found: {exc}")

print("exercised: skins.list (with thumb_size, limit, .first(), error handling)")
All endpoints · 1 totalmissing one? ·

Get all Piggy skins from the Skins navigation dropdown on the Category:Skins page. Returns each skin's name, thumbnail image URL, book (e.g. Skins | Book 1, Skins | Book 2, Skins | Extra, Skins | Community, Other Skins, PIGGY: Hunt Exclusive), and subcategory tab (e.g. Main, Alternate, Daily Quests, User Exclusive - Main, User Exclusive - Alternate). Results are returned in the order they appear in the navigation template.

Input
ParamTypeDescription
limitintegerMaximum number of skins to return.
thumb_sizeintegerThumbnail image width in pixels for scaling.
Response
{
  "type": "object",
  "fields": {
    "skins": "array of skin objects each containing name, image_url, book, and subcategory",
    "total": "integer total count of skins returned"
  },
  "sample": {
    "data": {
      "skins": [
        {
          "book": "Skins | Book 1",
          "name": "Piggy",
          "image_url": "https://static.wikia.nocookie.net/roblox-piggy-wikia/images/f/f8/PiggyRedesignNew.png/revision/latest/scale-to-width-down/200?cb=20250726023256",
          "subcategory": "Main"
        },
        {
          "book": "Skins | Book 1",
          "name": "Little Brother",
          "image_url": "https://static.wikia.nocookie.net/roblox-piggy-wikia/images/c/cc/LittleBrotherCurrent.png/revision/latest/scale-to-width-down/200?cb=20250729025116",
          "subcategory": "Main"
        },
        {
          "book": "Other Skins",
          "name": "Sketchy",
          "image_url": null,
          "subcategory": null
        }
      ],
      "total": 230
    },
    "status": "success"
  }
}

About the Fandom API

What get_skins Returns

The get_skins endpoint returns an array of skin objects sourced from the Skins navigation on the Piggy fandom wiki's Category:Skins page. Each object in the skins array includes four fields: name (the skin's display name), image_url (a direct URL to the skin's thumbnail), book (the grouping label such as Skins | Book 1, Skins | Book 2, Skins | Extra, Skins | Community, Other Skins, or PIGGY: Hunt Exclusive), and subcategory (the tab label, e.g. Main, Alte). The response also includes a total integer reflecting the count of skins returned in that call.

Filtering and Scaling

The endpoint accepts two optional input parameters. limit is an integer that caps how many skin objects are returned, useful when you only need a subset of the full collection. thumb_size accepts an integer pixel width to scale the returned thumbnail image_url, letting you request appropriately sized images for your UI without additional image processing steps.

Book Groupings and Coverage

Skins are organized into distinct book groupings that reflect how the Piggy game structures its cosmetics progression. These groupings — ranging from the base Book 1 and Book 2 through community-contributed and event-exclusive sets like PIGGY: Hunt Exclusive — are surfaced directly in the book field of each skin object. The subcategory field provides finer-grained tab-level classification within each book, allowing you to separate main skins from alternate variants.

Reliability & maintenanceVerified

The Fandom API is a managed, monitored endpoint for piggy.fandom.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when piggy.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 piggy.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
49m ago
Latest check
1/1 endpoint 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
  • Build a skin browser app showing thumbnails and names filtered by book grouping
  • Populate a Piggy game companion site with up-to-date skin imagery using scaled thumb_size values
  • Generate a checklist of all community and event-exclusive skins for completionist tracking
  • Cross-reference book and subcategory fields to classify skins by release era in a database
  • Feed skin names and image URLs into a Discord bot for Piggy cosmetic lookups
  • Sync a game wiki mirror with current skin inventory using the total count as a staleness check
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 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.

Frequently asked questions
Does Piggy Fandom have an official developer API?+
Fandom provides a general wiki API at https://www.fandom.com/api-help, but it is not specific to Piggy content and does not return structured skin data with book groupings or subcategory labels the way this API does.
What does the `book` field distinguish between, and can I filter by it?+
The book field identifies which grouping a skin belongs to: Skins | Book 1, Skins | Book 2, Skins | Extra, Skins | Community, Other Skins, or PIGGY: Hunt Exclusive. The endpoint does not currently accept a book filter parameter — it returns all skins and you filter client-side. You can fork the API on Parse and revise it to add server-side book filtering.
Does the API return skin unlock requirements, costs, or in-game descriptions?+
Not currently. The API covers name, image_url, book, and subcategory for each skin. Details like piggy token costs, unlock conditions, or lore descriptions are not included in the response. You can fork the API on Parse and revise it to add an endpoint that pulls per-skin detail pages.
How current is the skin list relative to the wiki?+
The API reflects the state of the Category:Skins navigation on piggy.fandom.com. New skins added to the wiki after a given call will not appear until the data is re-fetched. There is no built-in webhook or delta-sync; callers should re-query periodically to detect additions.
Does the API cover skins from related Piggy spin-off games or only the main game?+
The API covers skins listed under the main Piggy fandom wiki's Skins category, which includes PIGGY: Hunt Exclusive entries. Skins that exist only on separate wikis or are not listed in that category are not currently returned. You can fork the API on Parse and revise it to target additional wiki category pages.
Page content last updated . Spec covers 1 endpoint from piggy.fandom.com.
Related APIs in EntertainmentSee all →