Cards and printings
Manifest keeps two kinds of record apart: the card you play with, and the physical versions of it that exist.
Cards
A card is the game object: its number, category, colors, cost, power, counter and attributes. These are the same in every language. Names, traits and effect text sit under localizations, keyed by language.
curl "https://api.manifestcards.app/v1/cards/OP01-120" \
-H "X-API-Key: $MANIFEST_KEY"Printings
A printing is one physical version of a card, in one language, released in one product. OP01-120 Shanks has thirteen: six in English and seven in Japanese, across the original booster, later reprints and promos. Each printing has its own rarity, variant (base, parallel, reprint and so on) and image.
English and Japanese, linked
The same printing in both languages shares a group_id. Base printings link by card number. The rest pair up by product, rarity and position, and every pair is checked by comparing the artwork itself. A printing released in only one language has no group, and single_language is true.
curl "https://api.manifestcards.app/v1/printings?card=OP01-120&lang=all" \
-H "X-API-Key: $MANIFEST_KEY"IDs
Every record has an ID like crd_01m64rkxdcn221cab7nycmgytt: a prefix (set_, crd_, prt_ or pgr_) and a ULID. IDs never change and are never reused, so they're safe to store. Treat them as opaque: show the readable fields (number, code, official_id) and key your own data by ID.
Verification and provenance
Every record says how sure Manifest is about it in verification.status:
verified: every check agrees.auto_resolved: decided by a rule or a reviewed correction.reasonsays which.flagged: ambiguous or contradictory.reasonsays why. Flagged records are still served.
provenance lists the official pages a record was built from, when each was fetched, and a hash of exactly what was read.