HTTP
Many of the IoT devices also use HTTP as a connectivity option. Let's see what HTTP parameters could be configured.
Last updated
Was this helpful?
Many of the IoT devices also use HTTP as a connectivity option. Let's see what HTTP parameters could be configured.
Last updated
Was this helpful?
HTTP is very common as most of the web runs on it. The following fields could be configured in the IoTIFY HTTP client:
Protocol: Specify whether to use HTTP Secure or unsecured HTTP. It is always recommended to use secure HTTPS even if you don't have any security settings such as a password or preshared key.
Method: HTTP Rest method to use.
Endpoint: The Rest API path to which you are connecting. This field is also scriptable, which means you could dynamically change the path at the run time with a templated string such as http://httpbin.org/api/v1/{{state.endpoint}}
Timeout: The timeout value after which the iteration must be marked as failed if no response is received.
Additional Headers: Configure any additional REST headers here. They may be useful to pass any bearer tokens or other authentication headers. The fields in this are scriptable and could be used with templated strings such as "Bearer {{state.token}}"
IoTIFY also enables REST APIs usage within the device model functions. Check for more details.
