-remusr template: ster?clnt=<name|pass>&com=remusr[&<usr_1>=<str_pattern_1>&<usr_2>=...] Order of query params is not important. The user query parameters are optional. pattern : * | name descript: removes all records with stereotypes matching the stereotype pattern, for the specified user: either all stereotypes if pattern is '*', or a single stereotype, for the corresponding user. This is repeated for all parameters in the query string. The same user can de specified more than once in a query string. If no user query parameters exist, all the records in the table will be deleted (all user references to stereotypes). If no (user, stereotype) in DB matches the patterns, no record will be deleted (200 OK will still be returned). If the error code 401 is returned then no records have been deleted. example : ster?clnt=name|pass&com=remusr&john=*&george=visitor&george=expert ster?clnt=name|pass&com=remusr (deletes all records in table) returns : 200 OK, 401 (fail, request error), 501 (fail, server error) 200 OK : in this case the response body is as follows <?xml version="1.0"?> <?xml-stylesheet type="text/xsl" href="/resp_xsl/rows.xsl"?> <result> <row><num_of_rows>number of relevant rows</num_of_rows></row> </result> comments: the reference to the xsl file allows to view results in a web browser. In case the response body is handled directly by an application and not by a browser, this reference to xsl can be ignored.