Callback notifications for resources and lifecycle events
- Operations on resources
- Life cycle events
- Observed resources
IMPACT IoT sends the requested information in the form of asynchronous notifications on the callback URL of the client application.
Callback notifications describes the structure of the callback notification API.
Title | Callback notifications |
---|---|
URL | https://<netApp_callback_url> |
Method | POST |
Content-Type | application/json |
URL Params | None |
Data Params |
The following are the data parameters:
|
Success Code |
Response Code: 200 |
Error Code |
400: Bad request 401: Unauthorized 500: Internal network application error |
Sample Call | Curl:
|
Notes | None |
IMPACT allows controlling the payload size for the Application callback notifications. The payload size is set at a system level and can be overridden by the Application at registration.
For controlling the payload size at the user level, the user can configure the payload size
at the time of registration using the registration API using the optional
payloadSize
field, in Bytes.
For example:
PUT /m2m/applications/registration HTTP/1.1
Host: devlwm2m-edge-01
Authorization: Basic ZHRhZzpkdGFn
Content-Type: application/json
Content-Length: 153
{
"headers":
{"authorization": "Basic ZGVtbzpkZW1v"}
,
"url": "http://10.75.74.104:8503",
"payloadSize": 40000
}
maxBatchDataLength
present in the values.yaml of
impact-dc helm chart.For more information, see the section Sample values.yaml file in the Installation Guide.
Oversized uplink payloads
In cases where the payload cannot be segmented, for example, due to a large single encrypted uplink packet, the application may receive a payload greater than the maximum payload size.
Precendence order
The payload size from the API (user level) will get precedence over the system level limit.
If the payloadSize
is not provided for a user, IMPACT will use the system
level value for the user.