> For the complete documentation index, see [llms.txt](https://help.hummingbird.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.hummingbird.co/hummingbird-api/whats-the-difference-between-the-alerts-api-and-the-case-api.md).

# What’s the difference between the Alerts API and the Case API?

Currently the primary difference between the Alerts API and the Case API is the grouping behavior. Cases created via the Alerts API will include all alerts associated with a given subject. Cases created via the Case API are just created with the details provided in the request to Hummingbird. The grouping behavior of the Alerts API results in fewer cases and overall less work for investigators. We are also actively developing additional functionality to add intelligent handling to alerts registered over the Alerts API. For these reasons, we recommend using the Alerts API for alerts generated from any monitoring systems.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.hummingbird.co/hummingbird-api/whats-the-difference-between-the-alerts-api-and-the-case-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.