Online connection (Overview)

All Pou online functionality is handled by an HTTP server: http://app.pou.me/ajax

Requests

The requests are made using HTTP, and the connection is not encrypted. A request can be dissected in two sections: the URL parameters and the payload. The payload may not be present, as some requests don't require it.

Headers

Every request contains an entry for a cookie called unn_session.

Field	Notes
unn_session	This cookie is present in all requests. When the client is not logged in, the cookie is left empty.

Parameters

All requests have parameters about the version of the Pou client.

Field	Notes
_a	An indicator to access the API. This parameter is always set to 1 by the client. If not set, the server will return an HTML page.
_c	Unknown. This parameter has the value of the major version of the APK.
_v	The client version. This parameter holds the value of the minor version of the APK.
_r	The client revision. This parameter is usually set to the versionCode of the APK.

Responses

All responses must have a JSON payload with the data requested. If the request fails, the JSON payload will have an error entry with the following entries:

Field	Notes
type	The error type.
message	The message sent by the server. Although all errors have this entry, it is never checked by the client.

Example:

{"error":{"type":"UserNotLoggedIn","message":"You need to login to continue."}}

Note: some custom errors may have more entries than the listed above.