Resource Classes have a base data type declared by the data
keyword.
When used as an input, the API endpoint accepts the base data type by itself.
However, when used as an output, it’s wrapped in a container:
Here’s an example:
{
"data": { ... },
"links": {
"foo": "/bar/baz"
},
}
This provides a clear abstraction layer for implementing clients to work with, and the Veneto Toolkit or whatever
data
- the base data typeembedded
- an object containinglinks
- an object containing RC Links to other resourcesuri
- for embedded resources only - a string containing the URI for the resource