> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/fr/personal-account/developer.md).

# Développeur

La page développeur regroupe les différentes informations dont vous auriez besoin pour utiliser l'API REST de ngSurvey ou si vous souhaitez intégrer les sondages de ngSurvey avec [Zapier.com](https://zapier.com/developer/public-invite/73385/969b64f5042ca12ccdc64515da776dc1/).

## 🔅 Propriétés développeur

* **`Domaine REST`** domaine actuel sous lequel ngSurvey fonctionne.
* **`Endpoint REST API`** vous donne accès à l'API REST de ngSurvey et à la documentation de l'API.
* **`Clé REST API`** clé requise pour [accéder à l'API REST](/fr/personal-account/developer/api-connection-sample.md).
* **`ZAP de Zapier`** zaps préconçus pour  [se connecter à Zapier.com](/fr/personal-account/developer/zapier.com-connection.md).

   

{% hint style="info" %}
Vous pouvez modifier la route de la documentation Web de l'API REST vers une autre route de votre choix. Pour ce faire, ouvrez le fichier ngsurveysettings.json de votre installation et changez le **SwaggerRoutePrefix** vers une autre route.  
{% endhint %}


---

# 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.ngsurvey.com/fr/personal-account/developer.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.