The Wunderlist API Documentation
Switch branches/tags
Nothing to show
Clone or download
Latest commit bac47da May 24, 2018
Permalink
Failed to load latest commit information.
concepts Fix a typo Feb 8, 2016
endpoints Add author information to responses Nov 29, 2016
terms Update May 24, 2018
tools Renaming folders, taking the numbers out Oct 12, 2015
README.md Update May 24, 2018
index.md Renaming folders, taking the numbers out Oct 12, 2015

README.md

Wunderlist API Documentation

The Wunderlist API provides REST-based storage and synchronization of a user’s lists across multiple platforms and devices.

The primary things you’ll need to use it are an understanding of our data model, how we version individual entities in a user’s data, the formats we use for transmission, and a set of OAuth credentials.

Concepts

Endpoints

Tools

Wunderlist API Terms of Use

Usage of the Wunderlist API is governed by the Microsoft API License & Terms of Use.

Support

The source for this documentation in at GitHub. If you have questions or need to report an issue, please open an issue.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Compatibility

This API will evolve rapidly and future versions will add new endpoints and parameters. To provide a sane experience, the API is versioned. Within a version, the behavior and return values of the API will not change from currently documented behavior and return values. As well, the API and its data payloads are designed so that new parameters and return values can be added at any time.

To provide the best experience, a well-behaved Wunderlist API client must not send undocumented parameters as part of their request. These parameters could collide with a future version of the API. As well, a Wunderlist API client must accept and ignore any additional keys that it doesn’t handle in a response.

Security

It should go without saying, but all requests must be made using a secure connection. We support a minimum of TLS 1.0. We also recommend that you use certificate pinning in clients that you ship and which may operate on untrusted public networks.