Testing Device Manager Connectors and Location Engine Forwarders Using 3rd party tools.
Written by Iman Kareem
Updated at August 18th, 2026
Third-party tools like RequestBin, Beeceptor, and Webhook.site are great for testing and debugging. Thanks to their free tiers, anyone can dive right in and start playing around with integrations. These tools act as HTTP JSON listeners, making them a perfect match for testing Connectors and Location Engine Forwarders, which are also HTTP JSON-based.
Note: RequestBin is well known and usually the go to for developers. However, it requires a few additional steps to set up; which we will not cover in this article. There are plenty of tutorials online.
Also, the free tiers for these tools offer no or limit storage capabilities. The data records sent over may be automatically deleted after a few hours or days.
Beecepter lets you type in a prefix to make your own custom URL. e.g. tgwebhooktest1234.free.beeceptor.com.
Click Create Mock Server to continue.
Webhook.site randomly generates a URL when you open the website:
Testing a HTTPS JSON Connector with Webhook.site:
-
Create a HTTPS JSON Connector and use the URL provided by Webhook.site
Authentication and Headers are not required. However, a Header (TestHeaderName - TestHeaderValue) was added here for demonstration purposes.
2. Set the HTTPS JSON Connector on a device/s. (Standard GPS device like a Barra/Manta GPS, Yabby/Oyster/Remora 3 or a Vehicle Powered tracker).
3. View the data in Webhook.site.
The Device payload/record is show in the Content view below. And the Header details are shown in the top right.
Testing a Location Engine Forwarder with Webhook.site:
1) Create a Location Engine Forwarder and use the URL provided by Webhook.site
Authentication details and Headers are not required. However, a Header (TestHeaderName - TestHeaderValue) was added here for demonstration purposes.
When “OK” is clicked to complete the Forwarder set up, Location Engine will attempt to send some test/sample data contain recurring digit serial numbers like 222222 and 333333.
If a message stating “Successfully created forwarder.” appears, it confirms that the forwarder has been created successfully and that the test data was successfully delivered to the destination. In this case, Webhook.site returned an HTTP 200 OK response, confirming that the webhook request was received and accepted.
2) View the data in Webhook.site.
The test/sample device payload with a recurring digit serial (666666) is shown in the Content view below. And the Header details are shown in the top right.
3) Now that the Forwarder is working, the LE Forwarder must be ‘Assigned’. See Configuring Forwarders
4) A LE Connector will need to be created, and linked to the LE Forwarder that was created in Step 1. See Configuring Forwarders
5) Set the LE Connector on a Location Engine dependant device/s (Edge, Fusion, Recovery or Core Battery Powered device variants).
6) View the actual device data in Webhook.site.
Batch Mode
If the Batch Mode option is enabled while configuring the Forwarder, Location Engine sends a “list”/array of records processed at that point in time. The “list”/array can contain records from multiple serials/devices.
Example Payload:
