can be queried via an http API.
returns data about all the sets in the database.
returns data about all the cards in the database.
returns card data about the cards in the set identified by code
(core for Core Set, etc).
returns card data about the card identified by code
(01001 for Noise, etc).
returns name, author and composition of the decklist identified by id
(as found in decklist urls).
Data returned is in json format.
Set and card data include a "url" key giving the absolute url of the page that holds the data.
Card data include a "imagesrc" key giving the relative url of the image of the card.
Optional GET parameter "jsonp" for script tags.
returns data for Noise
returns data for all sets wrapped in a call to parseSets()
The response is in ascii encoding. Non-ascii characters are encoded with \uXXXX with XXXX their hexadecimal unicode value.
To test your application, 3 cards are useful:
- 02020 to test Unicode characters, [Credits] and [Subroutine] tokens, <strong> and <sup> markup for traces and keywords.
- 02046 to test Unicode characters, :, ", [Memory Unit] token-with-space
- 01036 to test ", ', &
- Card data include a "last-modified" key giving the timestamp of the data (CET)
- /api/cards/, /api/card/ and /api/set/ responses use both HTTP cache expiration (max-age) and cache validation (last-modified). Please use both when building your queries.
- All API responses include a CORS header: Access-Control-Allow-Origin:*
Embedded Display Mode
If the parameter "mode=embed" is added to an url, the page is served without the header and footer and navigation and search stuff, that is, with only the main content. See for example /card/01020?mode=embed
Add a parameter _locale=xx to get the results in xx locale.