Title: Methods
<a name="Methods-Methods,Resources,andDescriptions"></a>
## Methods, Resources, and Descriptions

*Bold* means the resource and method is implemented in the current /api2/
endpoint.

<table>
<tr><th> Resource </th><th> Method </th><th> Description/Payload schema/Response schema </th><th>
Streaming? </th><th> Admin Only? </th></tr>
<tr><td> *api2/session* </td><td> *GET*,*POST*,*DELETE* </td><td> Post parameter: token </td><td> </td></tr>
<tr><td> *api2/users* </td><td> *GET*, *POST* </td><td> Post parameters: nickname, password -
returns: user created </td><td> </td><td> *POST* </td></tr>
<tr><td> api2/users/USERID </td><td> GET </td><td> </td><td> </td></tr>
<tr><td> *api2/users/USERID/tokens* </td><td> *GET*, *POST* </td><td> Post parameters: description
- returns: token created </td><td> </td><td> *GET*, *POST* </td></tr>
<tr><td> *api2/user/messages* </td><td> *GET*,*POST* </td><td> Post parameters: message, via
(opt), pool (opt), realm (opt), metadata (opt), tags (opt), replyto (opt) </td><td>
*Yes* </td></tr>
<tr><td> api2/user/tags/TAG </td><td> GET </td><td> </td><td> </td></tr>
<tr><td> *api2/user/tags/TAG/messages* </td><td> *GET* </td><td> </td><td> Yes </td></tr>
<tr><td> *api2/user/followers* </td><td> *GET* </td><td> </td><td> </td></tr>
<tr><td> *api2/user/followees* </td><td> *GET*,*POST* </td><td> Post parameter: userId </td><td> </td></tr>
<tr><td> *api2/user/followees/USERID* </td><td> *DELETE* </td><td> </td><td> </td></tr>
<tr><td> *api2/user/tracks* </td><td> *GET*,*POST* </td><td> Post parameter: track (regex) </td><td> </td></tr>
<tr><td> *api2/user/tracks/TRACKID* </td><td> GET,*DELETE* </td><td> </td><td> </td></tr>
<tr><td> api2/user/tracks/TRACKID/messages </td><td> GET </td><td> </td><td> Yes </td></tr>
<tr><td> *api2/user/actions* </td><td> *GET*,*POST* </td><td> Post parameter: name, test, action </td><td>
</td></tr>
<tr><td> *api2/user/actions/ACTIONID* </td><td> GET,*PUT*,*DELETE* </td><td> Put parameter:
enabled (boolean) </td><td> </td></tr>
<tr><td> api2/messages/MESSAGEID </td><td> GET </td><td> </td><td> </td></tr>
<tr><td> api2/messages </td><td> GET,POST </td><td> </td><td> Yes </td></tr>
<tr><td> *api2/conversations/CONVERSATIONID* </td><td> *GET* </td><td> </td><td> </td></tr>
<tr><td> api2/conversations/CONVERSATIONID/messages </td><td> GET,POST </td><td> </td><td> Yes </td></tr>
<tr><td> *api2/pools* </td><td> *GET*,*POST* </td><td> </td><td> </td></tr>
<tr><td> api2/pools/POOLID </td><td> GET,DELETE </td><td> </td><td> </td></tr>
<tr><td> *api2/pools/POOLID/users* </td><td> GET,*POST* </td><td> Post parameters: realm, userId,
permission </td><td> </td></tr>
<tr><td> api2/pools/POOLID/users/USERID </td><td> DELETE </td><td> </td><td> </td></tr>
<tr><td> api2/pools/POOLID/messages </td><td> GET,POST </td><td> </td><td> Yes </td></tr>
</table>

One point to note is that some HTTP clients do not currently support the
"PUT" or "DELETE" methods, so these may have to be simulated through POST
methods with an extra parameter. I think that because of the close mapping
to resource verbs, is worth using these methods in the specification and
defining the simulation method for the entire API separately.