> For the complete documentation index, see [llms.txt](https://engyon.gitbook.io/engyon/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://engyon.gitbook.io/engyon/en/api/use-cases.md).

# Use cases

These pages describe the most common integration flows from start to finish. Each use case explains which endpoints you call, which data you need in advance, and which limitations you must observe.

| Use case                                                           | Description                                                                                                        |
| ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------ |
| [Creating a client](/engyon/en/api/use-cases/creating-a-client.md) | Setting up a client organisation, adding legal entities for a group with multiple entities, and assigning users    |
| [Creating an audit](/engyon/en/api/use-cases/creating-an-audit.md) | Creating a single or group audit, defining component audits (audit units), and coupling audits in an audit network |

### Other possibilities

The Engyon API supports more than the flows documented here. Depending on your service account roles, you can also work with audit content such as files, source records, scope, checks, and risks.

For the complete and up-to-date list of endpoints, request fields, and response schemas, use the interactive API reference: <https://audit.engyon.io/api/v1/docs/>

{% hint style="info" %}
The use case pages focus on how you combine endpoints into a working flow. Swagger remains the authoritative reference at the field level when something changes.
{% endhint %}