Best design approach for non-editable fields


#1

In our API, for individual members of a collection, we want to return the editable properties as well as the timestamps (created_at and updated_at) in the body of the 200 response.

But we don’t want to use those same fields in the actual body of the put response. (Since they are not editable.)

What’s the best way to, from a design standpoint, to setup our RAML for our resourceTypes, so that it covers this?

Here is what the resourceTypes section looks like now: gist