> For the complete documentation index, see [llms.txt](https://docs.halosecurity.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.halosecurity.com/docs/integrations/discovery-integrations/http.md).

# HTTP

Import assets into Halo Security from a plain-text file hosted online to keep your inventory up to date.

HTTP integrations enable you to automatically import assets from files hosted online. With HTTP integrations, you can dynamically generate a file to integrate any existing service with Halo Security and ensure an accurate and up-to-date asset inventory.

### Preparing an HTTP file

Start by hosting an HTTP file on the internet.

* The content type should be `text/plain`.
* The file should list IPs and/or hostnames, with each entry on a separate line.

An example file would look like this:

```
www.example.com
www2.example.com
111.111.111.111
```

### Add an HTTP integration

1. Visit your *Settings → Integrations →* [Add](https://app.halosecurity.com/user/settings/integrations/add).
2. Add the HTTP integration.
3. Add a name for your integration.
4. Configure the settings.

### Settings

* **Name:** An internal name for this integration. You can use multiple HTTP integrations for different URLs.
* **Auto Run:** Determines the frequency of adding assets from the file to your asset list.
* **URL:** The location of the file.
  * *Example:* `https://www.example.com/assets-list.txt`
* **Headers:** Optional HTTP headers for authentication or tracking.
* **Username / Password:** Optional basic HTTP authentication credentials for accessing the URL.
* **Ignored Assets:** Optional list of assets to ignore when parsing the file.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.halosecurity.com/docs/integrations/discovery-integrations/http.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.