ManaVault API v1.0 Documentation

1. Authorization

Authorization parameters are available at ManaVault Profile if API Access is obtained from Admin.

Each request except authorization is required to include 'access_token' parameter obtained from Authorization.

Access tokens are valid for 10 minutes from authorization and are not renewed if valid token exists.

API call number is limited to 600 requests per 10 minutes.

Explorer access:

Get access token

Authorization request:
    Form data:
Curl Example:
    curl -d "client_id=XXXXXXXXXX&client_secret=YYYYYYYYYY"

Example response:
    "data": {
        "access_token": "generated_access_token",
        "valid_until": "2023-10-04 06:08:39"

Example headers:
    HTTP/1.1 200 OK
    Date: Wed, 03 Oct 2018 20:05:46 GMT
    Server: Apache/2.2.22 (@RELEASE@)
    X-Powered-By: PHP/5.5.38
    Content-Length: 166
    Connection: close
    Content-Type: application/json

2. Endpoints available:

All available methods are listed below starting with •

(code) or (id) parameter within methods is required.

+ is an additional `fields` parameter and is included by adding ?fields=field1,field2,... to request url (see examples below).

Parameters can be user for fitering results. E.g. /edition/GRN/?fields=cost(2W) will return cards from Guilds of Ravnica having mana cost 2W.

• Endpoints list:
All available requests can be tested using ManaVault API Explorer

3. Endpoint request examples:

Example headers:
• List available editions:
• List all cards from Guilds of Ravnica with basic data:
• List all cards from Guilds of Ravnica with full data:
• List all Planeswalkers from Worldwake with full data:

4. Example error responses

Invalid access token:
Invalid field:
To many requests: