Header

Counts match the section lengths. Deliberately no timestamp: an unchanged registry produces a byte-identical file.

The first object in registry.json: the schema version, the source and a count per section. There is no timestamp, so an unchanged registry produces a byte-identical file.

Where it appears

registry.json → header
index.json carries the same counts under counts

Fields

Every field is present on every record; a value that does not apply is null, never missing. Types are from the release's schema; the schema itself is the contract.

Field	Type	Meaning
`schema_version`	integer	The shape of the file. Goes up when a field is added; a breaking change is a new major release instead.
`source`	string	The official API the data was read from.
`sets`	integer	How many records the sets section holds.
`cards`	integer	How many records the cards section holds.
`printings`	integer	How many records the printings section holds.
`slug_history`	integer	How many rows the slug_history section holds.
`name_history`	integer	How many rows the name_history section holds.
`card_history`	integer	How many rows the card_history section holds.

Example

Header · from release v3.4.0

{
  "schema_version": 12,
  "source": "https://api.sorcerytcg.com/api/cards",
  "sets": 6,
  "cards": 1100,
  "printings": 3088,
  "slug_history": 3088,
  "name_history": 1100,
  "card_history": 1129
}

Reference: registry API contract and published object definitions. Report a data or documentation issue.