# HTTP

![](/files/WfsCfSzVRKeFIwhmpN8a)

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.&#x20;

**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}}"**&#x20;

{% hint style="info" %}
IoTIFY also enables REST APIs usage within the device model functions. Check [here ](/additional-helpers/iotify-helpers.md#calling-http-rest-apis-rest-get-or-post-or-put-or-patch-or-delete)for more details.&#x20;
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.iotify.io/concepts/protocol-settings/http.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.