Transport via HTTP
An aspect can have multiple endpoints assigned to allow for more complex interactions than just
accessing the aspect data. Data retrieved from an endpoint must be encoded in JSON format, and
aligned to the Aspect Model corresponding to the aspect endpoint as described in
Payloads.
The following table describes the possible options for HTTP endpoints:
{tenant-id} - Unique identifier of the owning tenant.
Operation type | Mandatory | HTTP Verb | DTR Type | Path | Description |
---|---|---|---|---|---|
Retrieve aspect data |
|
|
|
Retrieve available data of an aspect according to the related Aspect Model. |
|
Filter aspect data |
|
|
|
Filter for specific information e.g., data between a defined time frame or to restrict the result to the desired information. |
|
Execute aspect operation |
(only if the Aspect Model defines operations) |
|
|
|
Execute an operation according to JSON-RPC 2.0 |