This is a heads up that the YQL
wrapper for the ESME API is starting to take shape. The structure of
the YQL abstraction mirrors the conceptual [API design on the cwiki|http://cwiki.apache.org/confluence/display/ESME/API+2.0+-+Design]
The Open data tables definitions are available at http://github.com/esjewett/yql-tables/tree/master
under the "esme" folder.
To quickly get it working, take the following steps:
1. Set up a token on the Stax deployment at http://esmecloudserverapache.dickhirsch.staxapps.net/
1. Go to the YQL console at http://developer.yahoo.com/yql/console/
1. Paste the following into the console to set up a session where
"token_value" is your token:
insert into esme.sessions (esme_api_endpoint,token) VALUES ("http://esmecloudserverapache.dickhirsch.staxapps.net/api/
1. Copy the session cookie out of the result. It looks something like the
following and is between XML tags "
Some notes: 1. This will work with any API endpoint. 1. The open data table files contain examples of all functions. It supports setting and destroying sessions, listing and sending message, listing all users, listing followers, listing followed, and following. 1. Unfollowing is mysteriously not working (it is timing out after 30000 ms). I'd love it if someone knew why this was happening, but otherwise I'll investigate further myself. 1. I'll be adding other API functions as I am able. 1. This is more of a conceptual exercise than anything else. I don't anticipate that it will significantly increase the usability of the API for developers, but it does expose a sort of command-line access to the API to more casual developers.