PalworldCenter

Public JSON API

Build on our card data

PalworldCenter is unofficial infrastructure you can actually use. If you're wiring a deck tool, a price bot, or a weekend project, hit /api/v1/ and you'll get JSON from the same catalog we show on the site. It's read-only. There isn't an admin surface here, and we don't hand out secrets.

Unofficial, with credit

Card names, stats, and images belong to Pocketpair, Inc. and Bushiroad Inc. We compiled facts for reference. Palworld and related marks are their trademarks. If you display this data, say it's unofficial and keep that credit nearby. Prices are market estimates, not appraisals.

Endpoints

  • GET/api/v1

    Index. Version, docs URL, and the list of endpoints.

  • GET/api/v1/sets

    Official sets. We skip unofficial TD03/TD04.

  • GET/api/v1/cards

    Cards with nested printings. Query: set, rarity, q, limit, offset.

  • GET/api/v1/printings

    One row per printing. Holo and base stay separate. Same filters as cards.

  • GET/api/v1/printings/{id}

    One printing plus the latest price snapshot, if we have one.

  • GET/api/v1/printings/{id}/prices

    Snapshot history. Sold comps show up when that table has rows.

  • GET/api/v1/meta

    Metagame overview behind /meta: archetypes, decks, card usage and matchups. Query: source (combined, human or sim), w (7, 30 or 90 days). A null is a number under its sample gate; the response lists the gates.

Filters

Cards and printings take the same query string. Official SKUs only. We won't return unofficial TD03/TD04 even if you ask.

  • set: set code, like EBP01
  • rarity: C, U, R, RR, SR, SP, SSP, SSS, and the rest of our rarity enum
  • q: name, card number, or slug search
  • limit / offset: page size caps at 100
curl "https://palworldcenter.com/api/v1"
curl "https://palworldcenter.com/api/v1/sets"
curl "https://palworldcenter.com/api/v1/meta?source=human&w=7"
curl "https://palworldcenter.com/api/v1/printings?set=EBP01&rarity=SSP&q=chillet"
curl "https://palworldcenter.com/api/v1/printings/1"
curl "https://palworldcenter.com/api/v1/printings/1/prices"

Deck codes

Sharing a decklist? There's an open standard for that: PWC1 deck codes are self-contained, URL-safe, and decodable in about a hundred lines. The site accepts them in the builder and generates them on every public deck page.

Be a good neighbor

Responses are cache-friendly. Please keep a copy for a few minutes instead of polling every request. There's a per-IP limit if you forget. CORS is open for GET. We don't take writes, and we don't include eBay listing caches or matcher rules.

Every payload includes an attribution object. Leave it in your logs, and surface the unofficial bit in your UI. Questions? support@palworldcenter.com.