A POST request to api/list with a timestamp attribute of latest article
would be replied with a JSON consisting of the following
| Key | Explanation | |
|---|---|---|
| 1. | r_timestamp |
the timestamp of the recieved request |
| 2. | u_timestamp |
the updated timestamp, i.e, the timestamp of the latest article being sent |
| 3. | num |
the total number of entries being sent |
| 4. | entries |
a list of articles |
Each article have the following keys
| Key | Explanation | |
|---|---|---|
| 1. | author |
the author of the article |
| 2. | key |
an identifier to be used in further request to api/news |
| 3. | kind |
the kind of article being sent. opinion/letter/op-ed etc. |
| 4. | timestamp |
the timestamp of the article being sent |
| 5. | title |
the title of the article |
A POST request to api/news with a key attribute of required article
(obtained from a request to api/list) would be replied with a JSON
consisting of the following
| Key | Explanation | |
|---|---|---|
| 1. | key |
The key of the article sent in the request |
| 2. | kind |
The kind of the article |
| 3. | snippet |
The html snippet of the article |
In case of errors, an empty JSON is received. If there is a client side error,
the received JSON consists of error attribute explaining the error.