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

# API

L'API REST di Devolutions Server consente alle applicazioni e agli strumenti di automazione di interagire a livello programmatico con casseforti, voci, utenti e impostazioni. Utilizzando chiavi API o credenziali applicative, gli script possono autenticarsi, elencare e aggiornare le voci oppure integrare Devolutions Server con sistemi esterni come piattaforme di ticketing o database di configurazione, con esempi dettagliati di richieste disponibili nella documentazione API integrata.

Uno schema comune consiste nell'utilizzare Devolutions PowerShell o una pipeline CI per creare voci standardizzate per i nuovi server, applicare tag e autorizzazioni e mantenere sincronizzati gli inventari esterni con il contenuto delle sue casseforti.

#### Argomenti correlati

* [Documentazione API](/server/it/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/it/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.