With either the GET or PATCH endpoint for the Conversations API, our event consumer code could remain stateless. We would like to either selectively update the necessary fields, or retrieve the current state, merge in the changes, and POST back the updates. But with only the POST, our event consumer code needs to maintain state across events, which adds a lot of unnecessary complexity to the solution.