> 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/fr/web-interface/help-and-tools/export/json-export-type.md).

# Type d'exportation JSON

Exportez vos données Devolutions Cloud au format JSON, en choisissant les coffres, dossiers et entrées, avec des options pour obscurcir les valeurs et inclure les pièces jointes.

Exportez vos données Devolutions Cloud au format JSON en suivant les instructions ci-dessous :

1. Dans ***Aide et outils***, cliquer sur ***Exporter***.
2. Sélectionner le type d'exportation ***JSON***.
3. Sélectionner le coffre à exporter (Devolutions Cloud seulement) et configurer les deux options connexes selon les besoins :
   * ***Obscurcir les valeurs sensibles*** : Rend votre information sensible plus difficile à déchiffrer. Pour des raisons de sécurité, il est recommandé de laisser cette option activée.
   * ***Inclure les pièces jointes et les documents*** : Permet d'exporter les pièces jointes et les documents contenus dans vos dossiers et entrées.
4. Sélectionner les dossiers et les entrées à exporter.
5. Cliquer sur ***Télécharger*** pour exporter votre sélection au format JSON.


---

# 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/fr/web-interface/help-and-tools/export/json-export-type.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.