> For the complete documentation index, see [llms.txt](https://docs.feedback.farm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feedback.farm/widget/build-your-own.md).

# Build your own

If the default widget doesn't fit your needs, you can build your own widget with the feedback.farm API.

{% hint style="info" %}
**Good to know:** You first need to create an account on [feedback.farm](https://feedback.farm).
{% endhint %}

## Configuration

Build your widget in the way you prefer. The only requirement is you need to be able to make a POST request.

* The http method is `POST`
* Endpoint URL: `https://api.feedback.farm/api/feedbacks/add`
* Content-Type: `application/json`
* The body is a stringified JSON with the following attributes:
  * projectId
  * feedback
  * identifier
  * type
  * pageName

Here's an example of a request with the required attributes in Javascript.

```javascript
fetch("https://api.feedback.farm/api/feedbacks/add", {
  method: "POST",
  headers: {
    Accept: "application/json",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ projectId, feedback, identifier, type, pageName }),
});
```


---

# 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.feedback.farm/widget/build-your-own.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.