Resource Class data

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:

Output data

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

List of fields