Yeah, I had forgotten to bring this up. So, I'm all for making "status_code" present on each request, instead of just including "error_code" when something goes wrong. The reason I added success_code to the success case was that I wanted to return a 202 when issuing a compaction job; however, the current flow does allow for that, and I didn't want to spend time on finding the "proper" way to get Cowboy to return the 202.

I can take the time to do it properly and get the 202 returning in the HTTP response, or we can punt that for later and just make "status_code" or "response_code" or whatever, be included on all response envelopes.

Thoughts @k-anderson?