# Test Endpoint

The Test Endpoint is designed to inspect the messages sent from your Flow.

## Configure your Test Endpoint:wrench:

1. Choose Test Endpoint as your destination.

<figure><img src="/files/5yAkOmWLZ8LwbAIFPbvi" alt=""><figcaption><p>Test Endpoint </p></figcaption></figure>

2. Type in your name for your new Test Endpoint and write your description to describe your current Test Endpoint.\
   \&#xNAN;**- `url:` used to send device-data to. Automatically filled in.**\
   **- `Shared Secret:`  Used for encryption & Validation. Automatically filled in.**

<figure><img src="/files/DbrF7Baz3vLrlpc57N7K" alt=""><figcaption></figcaption></figure>

3. Link your device to a flow. You'll also have to link your device(s) to your desired flow, before creating your Test Endpoint.

<figure><img src="/files/gtPspD117pn7qxhaqTOV" alt=""><figcaption></figcaption></figure>

4. Thats it! Now you should be able to find and view your Test Endpoint within your "Destinations" page. Feel free to make as many as you'd like.

<figure><img src="/files/EGUc3975B0uVCKa5WZiY" alt=""><figcaption></figcaption></figure>

5. View the messages that were sent to the Test Endpoint.

<figure><img src="/files/MHUQHrzfX4MOCSYzN8HS" alt=""><figcaption><p>Test Endpoint - Landing page</p></figcaption></figure>

### Restrictions:lock:

Be aware of the following constraints.&#x20;

* All messages expire after 5 days.
* A maximum of 100 most recent messages will be shown.&#x20;

### Page elements :pencil:

* **Messages:** Here you can view the messages that were sent to your Test Endpoint.
* **Details:** Contains the message ID and the timestamp when the message was received.
* **Headers**: The default HTTP headers that are sent to the Test Endpoint. These headers are the same default headers that a HTTPS Destination would receive.  Note that for a Test Endpoint these headers can not be customised, for a HTTPS Destination  you are able to add custom headers.
* **Content:** Contains the payload that was sent to the Test Endpoint. It matches the output of your decoders that was enabled in the flow. For the majority of cases, this payload will be SenML JSON data.  See: [SenML](https://docs.kpnthings.com/kpn-things/building-blocks/data-processing/thingsml-and-senml/senml)


---

# Agent Instructions: 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:

```
GET https://docs.kpnthings.com/kpn-things/building-blocks/destinations/test-endpoint.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.