HTTP Pull Listener

Most recent version: v0.0.7

Note that this Listener is only available in certain Tenants. Get in touch with us if you don't see it and want to access it.

Learn more about this Listener type in this article.

v0.0.7

Released on 04/23/2026

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.

v0.0.6

Released on 03/04/2026

• Duplicated query parameter keys are now allowed.

• BloodHound authentication is now supported.

v0.0.5

Released on 02/14/2026

• Implemented a retry mechanism for handling HTTP response failures.

• Akamai authentication is now supported.

v0.0.4

Released on 01/16/2026

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.

v0.0.3

Released on 11/18/2025

• 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.

v0.0.2

Released on 08/18/2025

• 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.

v0.0.1

Released on 05/12/2025

Initial version