@cheddar Yea, it was similar to what you detailed above. I began implementing the supporting function for the  `DELETE /user/:userid/deleteflag` route, but as I started thinking about the un-setting of the flag, I second guessed the use of DELETE. 

I thought of DELETE as a destructive call - i.e. it's only utilized when you are planning on removing/destroying/deleting whatever object corresponds to that request and there's no going back. With that in mind, I thought the POST/PUT (while still awkward at best) seemed more appropriate - we're not deleting the object referenced by the request, just setting a value on it.

That being said, I think that the DELETE/POST feels like a cleaner implementation of the HTTP method and route.