# HTTP

YuDash IoT devices support data push through REST POST API. Both HTTP and HTTPS (SSL) are supported.

**HTTP** is the default TCP/IP protocol for cloud communication. YuDash LYNX supports POST REST API for sending data to HTTP Server. The HTTP headers can be configured to support  various authentication types. 

Following are the settings in LYNX to configure connection to HTTP server:

<figure><img src="/files/bXiuV17k7IRCgETKt9nh" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="215">HTTP Parameter</th><th>Description</th></tr></thead><tbody><tr><td>HTTP Server</td><td><p></p><p>The URL of HTTP server is faccessible on the network. Alternately, unique IP address can be provided. This may be required for a local deployment.</p><ul><li>Remove any prefixes (http:// or https://) in the server name.</li><li>Remove any suffix APIs from server name. They are provided in API below.</li></ul></td></tr><tr><td>HTTP API</td><td>The API name (similar to subdirectory) which will accept POST request. This will typically start with "/".</td></tr><tr><td>HTTP Port</td><td>The port on which HTTP server is running.</td></tr><tr><td>HTTP Success Code</td><td>Success code REST API. This is used to check if POST command by IoT device was success or failure. This value has to be set as per cloud API. </td></tr><tr><td>HTTP SSL Enabled</td><td>Check this box for enabling HTTPS using SSL. This is recommended for production applications.</td></tr></tbody></table>

### **HTTP Headers for Authentication**

1. HTTP supports various authentication options. The authentication header keys and values are filled in section.&#x20;
   * These are sent as HTTP headers to server for handshake.
   * The UI supports two headers. In case multiple custom headers are required, it can be configured in JSON configuration.&#x20;

### &#x20;Device headers with HTTP Payload

In many HTTP servers, there may be single API accepting inputs from various sensors. So, it may be sharing credentials across a set of devices. In such cases, additional device information (say, machine name, sensorID, user-name) may have to be passed in JSON payload. This is besides the actual real-time data collected from sensors. For this requirement, there is an option to add device headers in JSON formats.

### SSL/TLS secure communication with HTTP

YuDash IoT devices support HTTP with SSL/TLS secure communication. Refer to [SSL/TLS for HTTP ](/device-to-cloud-api/cloud-protocols/ssl-tls.md#ssl-tls-for-http)documentation.

## LYNX Display with HTTP Post

Following are the typical LYNX display screens with HTTP POST

<figure><img src="/files/FNc1eOmOfkxtt8PUfmpN" alt=""><figcaption><p>LYNX attempting HTTP POST to a given API on port 443</p></figcaption></figure>

<figure><img src="/files/dEdlYhMxPJDycoPxSSxA" alt=""><figcaption><p>LYNX waiting for response from HTTP server</p></figcaption></figure>

<figure><img src="/files/1YRVfCPrnyyW2kgT2qtx" alt=""><figcaption><p>LYNX received HTTP response of 200, which matched with success code of 200</p></figcaption></figure>


---

# 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.yudash.com/device-to-cloud-api/cloud-protocols/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.