> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/de/concepts/advanced-concepts/api.md).

# API

Die REST-API von Devolutions Server ermöglicht Anwendungen und Automatisierungswerkzeugen die programmatische Interaktion mit Tresoren, Einträgen, Benutzern und Einstellungen. Mithilfe von API-Schlüsseln oder Anwendungsanmeldeinformationen können Skripte sich authentifizieren, Einträge auflisten und aktualisieren oder Devolutions Server in externe Systeme wie Ticketing-Plattformen oder Konfigurationsdatenbanken integrieren, wobei detaillierte Anfragebeispiele in der integrierten API-Dokumentation verfügbar sind.

Ein häufiges Muster ist die Verwendung von Devolutions PowerShell oder einer CI-Pipeline, um standardisierte Einträge für neue Server zu erstellen, Tags und Berechtigungen anzuwenden und externe Inventare mit dem Inhalt Ihrer Tresore synchron zu halten.

#### Verwandte Themen

* [API-Dokumentation](/server/de/web-interface/utilities/api-documentation.md)


---

# 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.devolutions.net/server/de/concepts/advanced-concepts/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.