Device to Cloud Supported Applications

Device to Cloud can integrate different application types and their communication protocols and data formats.

In Device to Cloud your applications are represented as “application entity” (AE) resources.

You can forward IoT device data or events to your application(s) by using “device groups” and assigning AEs to them.

You can add and configure AEs and device groups either via the Device to Cloud API or the GUI.

oneM2M API

oneM2M is a powerful framework to manage IoT assets, applications, configuration and IoT data.

The oneM2M API can be used as a generic interoperability layer to integrate different IoT devices, applications and platforms.

With Device to Cloud, you can use oneM2M to manage and communicate with IoT devices (uplink and downlink). This allows you to implement:

  • IoT applications;
  • adapters for existing applications;
  • software for processing data on edge gateways;
  • apps that run on devices, and
  • integrations with other oneM2M applications

Please refer to the Device to Cloud oneM2M API documentation for more details.

Webhook

A webhook is a very simple way to send real-time IoT data to your application using HTTP requests.

Integration is as easy as copying and pasting your webhook endpoint URL into Device to Cloud. The URL comprises all the necessary credentials.

In order to configure a webhook application Device to Cloud you must set the webhook URL as AE poa (point of access) attribute.

The application will receive a oneM2M notification.

Example:

  • Webhook call
POST HTTP/2
Accept: */*
Connection: keep-alive
Content-Type: application/json
X-M2M-Origin: /id-in
X-M2M-RI: 8892789079795726885
X-M2M-RVI: 3
Content-Length: 12345
 
{
  "m2m:sgn": {
    "nev": {
      "net": 3,
      "rep": {
        "m2m:cin": {
          "cnf": "application/json:0",
          "con": "... here comes the IoT device data ...",
          "cr": "CDevice-Provisioning",
          "cs": 346,
          "ct": "20250714T080359,198000",
          "lt": "20250714T080359,198000",
          "pi": "682f04532bf25265c89e9e44",
          "ri": "6874b9eff494e3fa1d7392e4",
          "rn": "f4d0c35b-4542-b68e-b340-db300983f5f9",
          "st": 2,
          "ty": 4
        }
      }
    },
    "sur": "d2c-dev-1/6874b9e5f494e3fa1d7392e2"
  }
}

Response key components:

  • m2m:sgn - oneM2M Signal/Notification wrapper
  • nev - Notification Event containing:
  • net - Notification Event Type (1=create, 2=update, 3=delete, 4=retrieve)
  • rep - Representation of the resource that triggered the notification
  • m2m:cin - Content Instance (IoT data container) with:
  • con - Content (the actual IoT device data)
  • cnf - Content Format
  • cr - Creator
  • cs - Content Size
  • ct - Creation Time
  • lt - Last Modified Time
  • pi - Parent ID
  • ri - Resource ID
  • rn - Resource Name
  • st - State Tag
  • ty - Type (4 = Content Instance)
  • sur - Subscription URI Reference