> 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/feeds.md).

# Feeds

Share data from your Halo Security account with other security tools.

Feeds provide a simple way to share Halo Security data with third-party security tools and services. Each Feed creates a dedicated, read-only URL that exports specific data types from your account in a format that's easy to consume by other applications.

## Use Cases

* Export asset lists to vulnerability scanners for comprehensive coverage
* Stream security events to SIEM platforms
* Share target information with network scanning tools
* Integrate asset data with configuration management systems
* Connect asset information with threat intelligence platforms

## Data Types

Feeds can export the following types of data:

* **Targets**: Information about monitored assets in your account, including hostnames, IP addresses, and associated metadata.
* **Assets**: Comprehensive data about discovered assets across your attack surface, including both monitored and unmonitored assets.
* **Events**: Security events and alerts generated by Halo Security's monitoring systems.

## Using Feeds

To get started with Feeds:

1. Navigate to *Events →* [Feeds](https://app.halosecurity.com/user/settings/feeds/) in your dashboard
2. Click the + icon to create a new Feed
3. Select the type of data you want to share
4. Configure any access restrictions
5. Use the generated URL to integrate with your tools

{% hint style="info" %}
**Note**: For more complex integration needs, consider using the full Halo Security [API](/docs/integrations/api.md).
{% endhint %}

## Security

Feeds are designed with security in mind:

* Read-only access ensures data cannot be modified through the Feed
* Optional IP address restrictions limit access to specific systems
* Each Feed uses a unique URL that can be revoked if needed

\\


---

# 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/feeds.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.