List sealed products

The only relation here is index: with include=index every row carries index_eur and last_price_at, at the same 1 credit per 50 products requested as the bare list. include=prices returns 400 INVALID_INCLUDE with details.prices_route: quotes are at GET /v1/sealed/{id}/prices (2 credits). Without an include the rows are catalogue only, and orderBy on those two fields is a 400. A single product on /v1/sealed/{id} always carries them.

Free text on the product name — in the locale given by lang, if any — or an exact sku. Not the card query grammar: there are no fields or ranges here, because "evolving skies booster box" is the whole question.

Set code, slug or alternate id, as on /v1/sets/{code}. Products of a set that is not in the catalogue carry set_code: null and cannot be reached this way.

Product kind, as printed in kind: BOOSTER_BOX, ETB, TIN, BLISTER, COLLECTION, BOOSTER_PACK, BOOSTER_BUNDLE, STARTER_DECK, BUILD_AND_BATTLE, PREMIUM_COLLECTION, SLEEVED_BOOSTER and twelve more. Read the values off the list rather than hardcoding them; an unknown kind returns an empty page, not an error.

Locale for name: en, ja, fr, de, es, it. A product without a name in that locale falls back to English.

release_date, name, sku, updated_at or set, and with include=index also index_eur and last_price_at, with a leading - for descending. Every order ends on sku as the tiebreaker.

Accepted snake_case spelling of orderBy; the same sort keys and cursor rules apply.

Rows per page, 1 to 250. Card and sealed lists cost 1 credit per 50 rows requested, rounded up: 50 costs 1, 51 costs 2, 250 costs 5, so ask for multiples of 50. Above 250 you get LIMIT_EXCEEDED — follow links.next instead of raising it.

Opaque keyset cursor from links.next. Never construct one; it carries the sort order it was issued for and is rejected if orderBy changes mid-run.

Send back the ETag you stored. The API returns a strong ETag on every catalogue response, and a 304 is a header exchange: no body, no database row read.