Test Endpoint
Last updated
Was this helpful?
Last updated
Was this helpful?
The Test Endpoint is designed to inspect the messages sent from your Flow.
Choose Test Endpoint as your destination.
Type in your name for your new Test Endpoint and write your description to describe your current Test Endpoint.
- url: used to send device-data to. Automatically filled in.
- Shared Secret: Used for encryption & Validation. Automatically filled in.
Link your device to a flow. You'll also have to link your device(s) to your desired flow, before creating your Test Endpoint.
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.
View the messages that were sent to the Test Endpoint.
Be aware of the following constraints.
All messages expire after 5 days.
A maximum of 100 most recent messages will be shown.
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:
