i like to file a request for a few new functions on the EBT-API. As some User parse the Web pages to generate statistics, i think it would be a good point to make the profiles available via the API.
Of course all the data-caching for the web pages should also apply for the following API-calls to not kill the database. Login should not be necessary for most of the calls.
I would like to have an API-call to get all the information about a given user. The parameter should be the user id. The reply should be a JSON-Hash with the values available on the page:
- user id
- user name
- hit count
- notes entered
- date of registration
- city id / city name (language?)
- country id / country name (language?)
- time stamp of last note
- (position on city/country/ebt-list, not sure about that)
The same request applies to the other profiles found on the page, namely:
- city profile
- region profile
- country profile
- note profile (with additional information if logged in, like a flag, if the note was already edited or not)
In a last step it would be great, if the lists of ebt would also be available as JSON the simplify the parsing for clients:
- user-csv (login required)
- zensored-user-csv (key required)
- hit-csv (really neccessary?, i think half of the list is unneeded anyway)
- all clients should use the https-version of the API, the http-version should be marked as deprecated.
- all clients should get a unique ID and identify themselves against the API
As this is quite a big set of request I would like to see them as a kind of time line. So in my opinion the priority could be from the top (more important) to the bottom (less important).
So whats your opinion?