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

# API

La API REST de Devolutions Server permite que las aplicaciones y las herramientas de automatización interactúen de forma programática con bóvedas, entradas, usuarios y configuración. Mediante claves de API o credenciales de aplicación, los scripts pueden autenticarse, listar y actualizar entradas, o integrar Devolutions Server con sistemas externos como plataformas de tickets o bases de datos de configuración, con ejemplos detallados de solicitudes disponibles en la documentación de la API integrada.

Un patrón habitual consiste en utilizar Devolutions PowerShell o un pipeline de CI para crear entradas estandarizadas para nuevos servidores, aplicar etiquetas y permisos, y mantener los inventarios externos sincronizados con el contenido de sus bóvedas.

#### Temas relacionados

* [Documentación de la API](/server/es/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/es/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.