JSON is used for the request and response format. JSON is a lightweight and portable format that maintains human-readability.
When making POST or PUT requests, the request parameters MUST be JSON-encoded and placed in the request body. When making GET requests, the request parameters MUST be JSON-encoded, then URI-encoded and placed directly in the query string.
Clients should expect JSON-encoded responses for every request, even those that result in an error.
Each method defines the HTTP method required depending on what the usage is. For example, if the method were used to simply get data, the HTTP method would be GET. If the method is used to delete data it uses DELETE.
The date and time MUST be expressed in RFC 3339 format: YYYY-MM-DDThh:mm:ssZ
Whenever an ellipsis ("…") appears in the JSON body, treat it as a placeholder for additional instances of the data that immediately precedes it.
The GET methods outlined in this document will use query strings, not JSON bodies, when making a request to a URL. This requires the user to convert JSON into a URL-encoded query string. Here's an example:
Minified fragment (using http://bigaqua.org/minify_json.html).
URL-encoded, minified fragment (using http://www.url-encode-decode.com/):
This URL-encoded, minified fragment is the query string. In order to compose a request, a "?" is appended to the end of the request URL, then the URL-encoded, minified fragment is added after that:
ON THIS PAGE