Docs

Use the v1 routes for integrations. The root path is the human-readable landing page.

Endpoints

GET /v1/sets
GET /v1/stats
GET /v1/quality
GET /v1/meta
GET /v1/cards
GET /v1/cards/:idOrSlug
GET /v1/images?ids=
GET /v1/images/:imageId
GET /v1/images/:imageId/manifest
GET /v1/images/:imageId/:rendition
GET /openapi.json
GET /llms.txt

Examples

curl https://api.tier4.club/v1/stats
curl https://api.tier4.club/v1/quality
curl https://api.tier4.club/v1/cards?limit=12
curl https://api.tier4.club/v1/cards/kpop-demon-hunter-classic-edition-1-en-kpdh01-hr-001
curl -I "https://api.tier4.club/v1/images/{imageId}?w=320&dpr=2"
curl https://api.tier4.club/v1/images/{imageId}/manifest

Operational Notes

• Responses include X-Request-ID for debugging.
• Errors include Problem Details fields and the legacy nested error object.
• Unsupported methods on known routes return 405 with an Allow header.
• Rate limit headers are emitted on public API responses, including RateLimit and legacy RateLimit-* fields.
• Image redirects use a separate images rate-limit bucket for grid-heavy frontends.
• Use cursor from card-list responses for stable pagination.
• Use numeric-only cardNumberShort for display and cardNumber for canonical matching.
• Use set show for franchise/IP labels and set name for the title.
• GET /v1/meta exposes safe client metadata for integrations and Codex.
• If API_KEY_HASHES or legacy API_KEYS is configured, /v1 routes require Authorization: Bearer or X-API-Key.
• API_KEY_HASHES supports labeled SHA-256 entries like label:sha256hex:1200.
• Image routes redirect to cacheable signed bucket URLs unless public image URLs are configured.
• Image redirect routes are browser-loadable without an API key by default, even when catalog JSON routes require auth.
• Image redirects support width and DPR hints, HEAD, ETag, Last-Modified, and selected-rendition X-Image-* headers.
• Use /v1/images/:imageId/manifest or batched /v1/images?ids=... when clients need responsive image metadata before rendering.
• Images are precompressed as WebP with optimized, preview, and thumbnail renditions.
• Card image records include responsive srcSet and sizes hints when rendition metadata is available.
• OpenAPI lives at /openapi.json.