# HTTP Listener

Learn more about this Listener type in [this article](https://app.gitbook.com/s/kxZeV4nlXcIAjMGZxzLI/the-workspace/listeners/listener-integrations/collect-data-using-http).

<details>

<summary>v1.5.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">03/11/2026</mark>

Improvements to error logging for debugging purposes.

</details>

<details>

<summary>v1.4.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">01/15/2026</mark>

* Added new error port.

</details>

<details>

<summary>v1.0.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">02/25/2026</mark>

Added the various authentication methods:

* basic authentication
* bearer token authentication
* API key authentication
* Added an *error* port when this Listener is used in a pipeline in order to eliminate data loss when an error occurs.&#x20;
* You can now capture and forward all HTTP headers from incoming requests by selecting **All** in the **Propagate headers strategy** configuration. When enabled, Onum automatically collects all request headers and makes them available in a consolidated **headers** field, preserving the complete header context throughout the processing pipeline without requiring manual specification of individual header names.
* The default header propagation strategy is back to **None**.
* Header names in the configuration are automatically converted to canonical form.&#x20;

</details>

<details>

<summary>v0.1.1</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">09/09/2024</mark>

Added strategy option to handle stacked JSON objects in a single request body. Example of request body:

```
{"data": "The first message"}{"data": "The second message"}{"data": "The third message"}
```

</details>

<details>

<summary>v0.1.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">09/06/2024</mark>&#x20;

`host` has been removed from metadata parameters and now uses `0.0.0.0` by default.

</details>

<details>

<summary>v0.0.1</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">07/28/2024</mark>

Initial version

</details>
