The JSON Schema is https://entrecode.de/schema/datasource.
|dataSourceID||String||Version 4 UUID (RFC 4122)||The unique identifier for a DataSource||No. Gets generated on creation.|
|dataSourceType||String||valid dataSourceType||Specifies the type of the DataSource.||Yes.|
|config||JSON Object||valid against the JSON Schema of the selected dataSourceType||dataSourceType-dependent configuration options.||Yes.|
|Relation Name||Target Resource||Description||Possible Methods|
|self||DataSource||The resource itself||GET, PUT, DELETE|
|collection||DataSource List||List of all available DataSources||GET, POST|
|ec:app||App||The app this dataSource is corresponding to.||GET, PUT, DELETE|
|ec:app/platform||Platforms||Platforms that use this dataSource. (optional)||GET, PUT, DELETE|
Note that a dataSource cannot be deleted if it is used in at least one platform.
The DataSource List Resource is a Generic List Resource with embedded DataSource Resources.
To read a single DataSource Resource, clients may perform GET on a
To read the DataSource List Resource, clients may perform GET on a
ec:app/datasources relation or on the
collection relation of a single DataSource resource.
In both cases, the success status data is 200 OK.
To create a new DataSource Resource, clients may perform a POST on
ec:app/datasource (the list resource). The JSON Schema for creating a new DataSource is https://entrecode.de/schema/datasource-template.
The success status data is 201 Created and the response body is the newly created single DataSource resource.
To update an existing DataSource Resource, clients may perform a PUT on
self at a single DataSource Resource. The JSON Schema for editing an DataSource is https://entrecode.de/schema/datasource-template.
The success status data is 200 OK and the response body is the updated single DataSource resource.
To delete an existing DataSource Resource, clients may perform a DELETE on
self at a single DataSource Resource. This is only possible if the dataSource is not used in any platform (would trigger an error 403 with code 3370).
The success status data is 204 No Content with an empty response body.
All DataSource types SHOULD contain a required property
hexColor in the config_schema.
hexColor SHOULD be the regex format
Pulls data out of a Data Manager.
Expected configuration: a JSON object with the key
url is needed, linking to the generated API of the Data Manager, and the key
hexColor, with the desired color shown in the editor frontend (format: