> For the complete documentation index, see [llms.txt](https://docs.loadmill.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.loadmill.com/reporting/api-catalog-and-coverage/api-catalog/endpoints-grouping.md).

# Endpoints grouping

By default, nested API's will appear under the first recognized category (skipping versions), which can be refined.

<figure><img src="/files/6gleF6VKU1mXq4F8mkQi" alt=""><figcaption><p>By default, the marked api's will be grouped under users category as it comes first in the path.</p></figcaption></figure>

In order to specify which categories should be skipped in grouping follow the next steps:

1. Head to "settings", in the dotted menu at the top-right corner of the screen

   <figure><img src="/files/gUco680INbv3ojc9Nuaa" alt=""><figcaption></figcaption></figure>
2. In "PER-SERVICE", under "Ignored Path Elements" add the parts they should be skipped.\
   ie. 'users'

<figure><img src="/files/9rPgP9uLzQFprkvHzDoz" alt=""><figcaption></figcaption></figure>

3. To apply changes on existing domains, check the box "Apply changes to existing APIs".
4. Click on save

<figure><img src="/files/j6d0Ya3QFt3BoMM75tDS" alt=""><figcaption><p>The result will be new grouping by the next possible path section</p></figcaption></figure>


---

# 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://docs.loadmill.com/reporting/api-catalog-and-coverage/api-catalog/endpoints-grouping.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.