# HTTP Pull Listener

{% hint style="warning" %}
Note that this Listener is only available in certain Tenants. [Get in touch with us](/support/support.md) if you don't see it and want to access it.
{% endhint %}

Learn more about this Listener type in [this article](/the-workspace/listeners/listener-integrations/pull-data-from-http-endpoints.md).

<details>

<summary>v0.0.7</summary>

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

We have added the option to stop the Listener so that it is inactive and therefore does not retrieve data from endpoints. Before, the only option was to delete the Listener or the Pipeline containing the Listener, whereas now the **Stopped** option allows for temporary actions.

</details>

<details>

<summary>v0.0.6</summary>

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

* Duplicated query parameter keys are now allowed.
* BloodHound authentication is now supported.

</details>

<details>

<summary>v0.0.5</summary>

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

* Implemented a retry mechanism for handling HTTP response failures.
* Akamai authentication is now supported.

</details>

<details>

<summary>v0.0.4</summary>

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

If you select pagination as *none,* which means only a single request is issued, you can now choose whether to repeat the request until no data is returned.

</details>

<details>

<summary>v0.0.3</summary>

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

* Added syntax and semantic verification for JQ expressions used in HTTP pull operations. This prevents runtime failures, improves data pipeline reliability, and provides immediate feedback when configuring JSON transformations for pulled HTTP data.

</details>

<details>

<summary>v0.0.2</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">08/18/2025</mark>

* New HMAC authentication added
* Throttle and Retry parameters for Collection and Enumeration phases to control resource usage and error handling. **Throttle Parameters** limit the rate of operations during Collection and Enumeration phases to prevent system overload. These include maximum requests per second, concurrent connections, or bandwidth limits. **Retry Parameters** define how failed operations are reattempted, including retry count and backoff intervals.&#x20;

</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;">05/12/2025</mark>

Initial version

</details>


---

# 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.onum.com/listeners/http-pull-listener.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.