APIs
Name |
Description |
Default URL prefix |
Status |
|---|---|---|---|
Deprecated - This is our original "REST-like" API |
/api |
Available |
|
Current - This is our newest API that deals allows for streaming-based access |
/api2 |
Available |
|
Twitter - We also support the Twitter API which allows for clients that support laconica to also use Apache ESME |
/twitter |
Available |
|
This is an API that will users to access JMX-based |
/jmx |
Currently being designed |
Note: It is possible to change the used URL prefixes for the individual APIs via properties.
Using an API
Clients should be developed using /api2.
If you wish to use a API, then you must take the server name and add the URL prefix.
For example, http://esmecloudserverapache.dickhirsch.staxapps.net/twitter
Token
All these APIs require that you use a token.