Mobile Vikings API

The Mobile Vikings API is organized around REST. Our API is designed to have predictable, resource-oriented URLs and to use HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs, which can be understood by off-the-shelf HTTP clients, and we support cross-origin resource sharing to allow you to interact securely with our API from a client-side web application (though you should remember that you should never expose your secret API key in any public website’s client-side code). By default, JSON will be returned in all responses from the API, including errors.

We have a Mobile Vikings Developers group. Feel free to subscribe to our group to keep up with new features that don’t happen to break existing code.

Current Version

The current version of the API is v3. By default, all requests receive the latest updates of our api. When we make backwards-incompatible changes to the API, we release new dated versions. All requests must be prefixed with: