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

# API

Manage Devolutions Cloud through the Devolutions PowerShell module to automate entries, vaults, and users via PSHubContext authentication.

Administrators access the Devolutions Cloud API primarily through the Devolutions PowerShell module, which exposes cmdlets for managing Devolutions Cloud data from PowerShell. Using PSHubContext objects, scripts authenticate with an application user and secret, then call commands to create, update, or remove entries, vaults, and users in an automated way.

In daily operations, this API surface is used to integrate Devolutions Cloud with deployment pipelines, CMDBs, or reporting systems. For example, you can use the PowerShell script export type to generate JSON or CSV data and feed it into external analytics, or automatically provision new project vaults and assign groups based on a standardized script.

#### Related topics

* [Devolutions Cloud PowerShell](https://docs.devolutions.net/powershell/devolutions-cloud-powershell)
* [PowerShell module](https://docs.devolutions.net/powershell/devolutions-cloud-powershell/powershell-module)
* [PowerShell script export type](/cloud/web-interface/help-and-tools/export/powershell-script-export-type.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/cloud/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.