> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/nl/features/gerer-le-consentement-aux-cookies/integration-technique/comment-tester-lintegration-dun-widget.md).

# Widget integratie testen

## Voorbeeldmodus activeren

![](/files/JLBpboJj63AiGaT1JYCR)

Voorbeeldmodus zal de widget cache deactiveren en je toestaan om je configuratiewijzigingen live te bekijken. Localhost domeinen zullen ook geauthoriseerd worden.

## Je kunt de volgende api sleutel gebruiken

```
dastra00-0testing1-key
```

{% hint style="info" %}
Deze toets geeft een voorbeeld van een toestemmingswidget weer. Het is niet mogelijk om de configuratie aan te passen. Het doel van deze sleutel is om integratietests uit te voeren (bijvoorbeeld in een jsFiddle).
{% 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 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://doc.dastra.eu/nl/features/gerer-le-consentement-aux-cookies/integration-technique/comment-tester-lintegration-dun-widget.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.