TCGdex

Gotchas & limits

• The locale is a first-class path segment, and getting it wrong produces a different error type than a bad card id, not the same 404. A live GET this run against /en/cards/nosuchcard returned HTTP 404, 171 B, a problem-document shape: {"type":"https://tcgdex.dev/errors/not-found","title":"The resource you are trying to reach does not exists","status":404,"endpoint":"/en/cards/nosuchcard","method":"GET"}. Swapping the locale for an invalid one instead (/zz/cards/swsh3-136) returned a different 404, 355 B: {"type":"https://tcgdex.dev/errors/language-invalid","title":"The chosen language is not available in the database","status":404,"endpoint":"/zz/cards/swsh3-136","method":"GET","lang":"zz","details":"You must use one of the following languages (en, fr, es, es-mx, it, pt, pt-br, pt-pt, de, nl, pl, ru, ja, ko, zh-tw, id, th, zh-cn) while you used \"zz\""} — code that only checks status === 404 can't tell a typo'd id from a typo'd locale without reading type.
• GraphQL is served on the same host at /v2/graphql, but a plain GET to it does not run your query — a live GET this run against /v2/graphql?query={__typename} returned HTTP 200 with 1,694,752 B of text/html (the GraphiQL IDE page), not a JSON result. Queries need a POST with a JSON body.
• Asset URLs embedded in card/set objects (like image above) are deliberately incomplete — they resolve to a real image only after appending /{quality}.{format} (e.g. /high.png, confirmed live 200 image/png 327,364 B this run); fetching the bare URL from the object is a confirmed live 404.
• The response content-type includes charset=utf-8 explicitly (application/json; charset=utf-8, confirmed on both the card and the error responses this run) — an exact-match check against application/json alone will fail.