Character Set

Toodledo uses UTF-8 for all character encodings. Communication to and from Toodledo should be done with UTF-8.

GET vs POST

Our API will allow any request via either GET or POST. However, you should keep in mind that the maximum length of a GET request is around 2000 characters (depending on the client). For submitting information to Toodledo that could contain more than 2000 characters, you should use POST. When using GET, you can use either ; or & to separate parameters. When using POST, you should only use &.

SSL Connections

SSL (https://) connections are always supported and should be used whenever possible to protect user's data.

JSON Encoding

JSON is a lightweight text-based open standard designed for human-readable data interchange. It is derived from the JavaScript scripting language for representing simple data structures and associative arrays, called objects. Despite its relationship to JavaScript, it is language-independent, with parsers available for most scripting languages. --Wikipedia

Toodledo uses normal encoding for JSON objects. This means that the " and \ characters can be escaped with a backslash: \" or \\. They can also be escaped with their Unicode values: \u0022 or \u005C. Other characters can be left unencoded or optionally encoded with their \u#### Unicode escape sequences.

URL Encoding

Any string that you transmit to Toodledo must be encoded such that all non-alphanumeric characters (except -_.~) have been replaced with their %XX equivalent. This is the encoding described in RFC 3986. Spaces may be encoded as either + or %20.

PHP Example

Putting it all together, here is a simple PHP example that demonstrates JSON and URL encoding.