The following pages and posts are tagged with
| Title | Type | Excerpt |
|---|---|---|
| HTTP API concepts | Page | Ditto’s HTTP API follows some concepts which are documented on this page. The entry point into the HTTP API is: http://localhost:8080/api/<apiVersion> API versioning Ditto’s HTTP API is versioned in the URL: /api/<apiVersion>. Currently Ditto distinguishes between deprecated API version 1 and API... |
| HTTP API Messages | Page | The HTTP API allows sending Messages to and from Things and its Features. To dive into the basic concepts of the Messages functionality, please have a look at the Messages page. Tip: Check out the WebSocket Messages API if you also need... |
| HTTP API overview | Page | Ditto’s HTTP API is documented separately in the HTTP API Doc. There you can explore the two different API versions (the difference is described in the Basic Overview). Ditto does not provide a fully compliant RESTful API in the academic sense as it does not include hyperlinks... |
| WebSocket protocol binding | Page | Ditto Protocol messages can be sent as is as WebSocket message. The Ditto Protocol JSON must be sent as UTF-8 encoded String payload. WebSocket features The WebSocket provides an alternative to the HTTP API in order to manage your digital twins. The benefits of the... |
| HTTP API search | Page | The search aspect of Ditto can be accessed via an HTTP API. Note: Find the HTTP API reference at the Search resources. The concepts of the RQL expression, RQL sorting and RQL paging are mapped to HTTP as query... |
| HTTP API server sent events (SSE) | Page | Server-Sent Events (SSEs) can be used to get notified when the state of digital twins change, and to receive a search results stream. Server-Sent Events Server-Sent Events are... |