v4.1.0

4.1.0: seller country, sale type and comp currency (#13)

EbayListing gains currency, seller_country and sale_type. Card comps from
ebay.de and ebay.es are priced in EUR, so currency has to be read per row.
CardmarketListing gains seller_country.

New listing filters:
- seller_country and exclude_seller_country on the eBay and Cardmarket
  listings for cards and sealed. They take an array or a comma-separated
  string, and arrays are joined with commas on the wire.
- grade_qualifier on card eBay comps: pristine, black_label or none.
- sale_type on card eBay comps, one value or an array.

ErrorCode adds missing_api_key and invalid_api_key, which the API now sends
on a 401 instead of unauthorized. The README covers the new fields, Spanish
cards, and the updated meaning of an unknown attribution.

Everything is additive, so this is a minor bump.

Verified with npm run typecheck and npm run build.

v4.0.0

4.0.0: TCGplayer total_asc/total_desc sorts, drop sale_count (#12)

* 4.0.0: TCGplayer total_asc/total_desc sorts, drop sale_count

TcgplayerSort gains total_asc and total_desc, which the API now accepts on
both TCGplayer listings endpoints: they order by price + shipping_price, the
order TCGplayer's own site uses, where price_asc orders by item price alone.

PriceHistoryPoint loses sale_count. The API removed it: it counted our daily
price snapshots (normally 1) and was being read as sales volume. Removing a
field from a public interface is the major bump.

Verified with npm run typecheck and npm run build.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TzmZo2tRyS2mzKWeLtSDiu

* Catch up on API fields the SDK never learned

An audit of every public response struct and query parameter against the
SDK types found four gaps, all older than this release:

- docs_url on error bodies was parsed away. It is now docsUrl on every
  PkmnPricesError, null when there was no body to read it from.
- grade_qualifier on eBay comps: Pristine and Black Label tens carry the
  same grade as a plain ten and sell well above it.
- condition and variant filters on price history.
- grader filter on the card list, beside the grade filter it already had.

Verified with npm run typecheck and npm run build.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TzmZo2tRyS2mzKWeLtSDiu

---------

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>

v3.4.0

Release 3.4.0 (#11)

#10 shipped the sealed Cardmarket listing methods and the opened and
sell_count fields but left the version at 3.3.0, so npm still serves a
3.3.0 that does not have them. Nothing is published until the version
moves.

Minor rather than patch: sealed gained cardmarket/iterateCardmarket/
allCardmarket and CardmarketListing gained two fields. Every addition,
nothing renamed or removed, so a 3.3.0 caller keeps working.

v3.3.0

Release 3.3.0 (#9)

#8 added fields and filters and left the version at 3.2.0, so the published
package would have claimed to be what it was before: EbayListing gained
variant, attribution and ingested_at, TcgplayerListing gained snapshot_at, and
the eBay params gained variant and since.

All additive, so a minor.

v3.2.0

Carry Cardmarket's signed, altered and graded flags (#7)

* Carry Cardmarket's signed, altered and graded flags

The API returns these per-listing attributes now. An offer carrying any
of them is real and is returned, but it does not contribute to the card's
market price, which means the cheapest row the SDK hands back is not
necessarily the card's market_price. That is easy to get wrong and was a
live pricing bug before the pipeline learned to tell these apart, so the
README states it outright and shows the filter.

* chore: release v3.2.0

v3.1.0

Additive release on top of 3.0.0.

What's new

• Pass currency on sealed product get/list, and type the Cardmarket fields (#3)
• Support Cardmarket current prices and listings (#4)
• Add sealed product listings (#5)

Note on versioning

This package has been on the 3.x line since the two breaking changes in #1 and #2. Earlier releases were mislabelled as v1.0.x even though they published 3.x artifacts to npm — the release tag is only a label, and the workflow publishes whatever version package.json carries. Tags now match the published version, and the publish job fails fast if they ever drift again.

Full Changelog: v1.0.5...v3.1.0

v1.0.4

feat: expose Cardmarket mapping (v1.0.4)

v1.0.3

feat: add tcgplayer card listings endpoint (v1.0.3)

Add CardListingsResource.tcgplayer / iterateTcgplayer / allTcgplayer
backed by GET /v1/cards/:id/listings/tcgplayer, with TcgplayerListing,
TcgplayerListingsParams, and TcgplayerSort types. Params mirror cardmarket
except variant -> printing. Bump version to 1.0.3.

v1.0.2

feat: card attributes + /cards attribute filters, v1.0.2

Add rich card attribute fields (stage, card_type, weakness, resistance,
retreat_cost, energy_type, ability, flavor_text, attacks) to the Card
type and stage/card_type/weakness/energy_type to ListCardsParams.

v1.0.1

chore: add repository metadata, bump to 1.0.1

Add repository, homepage, and bugs URLs to package.json so the
GitHub repo link surfaces on the npm package page. Bump version
to trigger a publish that carries the new metadata.