API Documentation >> API 2.0 Main
This is the main page for Cardmarket's RESTful API version 2.0 (release1).
If you're using the API version 1.1 (current build 1.1.1), please refer to the 1.1 Documentation.
Welcome to the first release version of Cardmarket's API 2.0.
Read more about the Sandbox and it's requirements at the Sandbox Server Documentation.
With the introduction of the 2.0 version all versions of the API will run parallel on our servers.
Once 2.0 hits the live servers, we'll discontinue support for 1.0, while support for 1.1 will last until the next major API version. Nevertheless you can still access all 1.0 requests as normal.
With 1.1 we changed the way of authentication against the API and everything you need to know about our implementation of OAuth and how to use it, you'll find in the dedicated Authentication Documentation.
To create an app (either Dedicated, 3rd Party, or Widget App) login to your account at the normal (sandbox) website and go to your profile page. Here you'll find the option for creating one.
Cardmarket API and its resources is basically parted into the following sections:
You'll find an overview description of the different requests (and the links to the detailed description) at the respective section pages.
With 1.1 we introduced JSON as an additional response format for all requests. You can choose between XML (still standard) and JSON. If you decide for JSON, simply use the switch
output.json between the base URI and the resource URL.
GET https://sandbox.mkmapi.eu/ws/v2.0/gameswill return Cardmarket's supported games as XML (because XML is standard).
GET https://sandbox.mkmapi.eu/ws/v2.0/output.xml/gameswill return Cardmarket's supported games as XML.
GET https://sandbox.mkmapi.eu/ws/v2.0/output.json/gameswill return Cardmarket's supported games as JSON.
You'll find a list of all entities that are returned by the various requests at Entities Documentation. With 2.0 we not only introduce HATEOAS links within each response entity, but also changed the structure of entities themselves. In most cases 2.0 entities are not compatible with the 1.1 (and 1.0), so before switching to the 2.0 requests, make sure your app and processing response entities is revisited.
Document written on September, 30th 2015