> 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/da/concepts/advanced-concepts/api.md).

# API

REST API'en i Devolutions Server lader programmer og scripts administrere bokse, poster, brugere og indstillinger programmatisk ved hjælp af godkendte API-nøgler.

REST API'en i Devolutions Server gør det muligt for programmer og automatiseringsværktøjer at interagere programmatisk med bokse, poster, brugere og indstillinger. Ved hjælp af API-nøgler eller programlegitimationsoplysninger kan scripts godkende, liste og opdatere poster eller integrere Devolutions Server med eksterne systemer som ticketsystemer eller konfigurationsdatabaser, og detaljerede anmodningseksempler findes i den indbyggede API-dokumentation.

Et almindeligt mønster er at bruge Devolutions PowerShell eller en CI-pipeline til at oprette standardiserede poster til nye servere, anvende mærker og tilladelser og holde eksterne inventarlister synkroniseret med indholdet i Deres bokse.

#### Relaterede emner

* [API-dokumentation](/server/da/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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/server/da/concepts/advanced-concepts/api.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.