> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/help-and-faq/request-documentation.md).

# Request documentation, suggest features, or send feedback

Learn how to request documentation, send feedback or make a feature request directly on the Digibee Integration Platform.

On the Digibee Integration Platform, you can request new documentation or updates on existing documentation, suggest a new feature or provide feedback about your experience with the Platform. Follow the step-by-step below to learn how to submit your feedback within the Platform.

1\. Go to the Digibee Integration Platform homepage.

2\. Click the **question mark icon** in the upper right corner of the screen.

3\. Select the **Send Feedback** option.

4\. You will be redirected to the [Digibee Customer Feedback page](https://digibee.atlassian.net/servicedesk/customer/portal/6).

<figure><img src="https://content.gitbook.com/content/jvO5S91EQURCEhbZOuuZ/blobs/Fuh4bbObVD32IOHc7IOW/Documentation_requestENG.gif" alt=""><figcaption></figcaption></figure>

You can also request documentation by clicking on the **Request documentation** button on the top right corner of the Digibee Documentation Portal.


---

# 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.digibee.com/documentation/help-and-faq/request-documentation.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.
