...

The "type" should always be a StudlyCase name of an entity that exists in our Ubiquitous Domain Language/wiki/spaces/BPLAT/pages/38539005, for example: "ExternalVODProductMapping" or "User"

...

This only becomes relevant when the client is interested in the identity of the entity.  For the most part the client is likely to be uninterested, but we want to allow the client the ability to treat a REST entity as an entity (whose identity is independent of it's value) rather than value objects if they so choose.

Time values

Time values SHOULD be unix epoch integer timestamps

Hydration

Every API MUST avoid retrieving data from the database unless it is directly relevant to the API endpoint

...