Proxy Endpoint

Detailed description of how the proxy endpoint works and its configuration.


This endpoint acts as a proxy for an endpoint running on your local server within the Slingr platform. It’s primarily designed for endpoint development. For more details, refer to the “Create Your Own Endpoint” section.


Endpoint URI

The endpoint URI is the address at which both the external service and Slingr can locate your local endpoint. This should be a public URL (you might need to set up port forwarding on your router). It should point to the TCP port specified by _webservices_port (default TCP port 10000). Alternatively, you can use ngrok for added convenience, which creates a secure tunnel to your localhost.

Endpoint Token

This token serves as a verification mechanism for validating messages sent to and received from the proxy endpoint. While we recommend using the auto-generated token, you have the option to modify it if needed. This token will be part of your local endpoint configuration (see below).

Local Endpoint Configuration

Here is the fundamental configuration that should be applied to your local endpoint. Consult the SDK documentation you’re using to find out where this configuration needs to be placed.

Javascript API

The Javascript API is determined by the functions and scripts within your endpoint. To understand the range of possibilities, please review the “Endpoint Features” section.


Events are specified within your endpoint’s configuration file. For more details, refer to the “Endpoint Features” section.