Configuration
To set up Event Sink, make sure to have your full publicly accessible endpoint ready (e.g. https://my-domain.com/event).

Endpoint URL
Use this field to specify the full URL of the endpoint you would like to send EdgeTag event payloads to.
The endpoint itself should receive POST requests with a JSON payload and respond with a 200 OK response. The response body will not be used, but the response code will be used to determine whether the event was delivered successfully or not.
Event name filter
You can choose to limit events being sent by their event name. You can select or specify any number of event names you would like us to send to the endpoint, or you can leave this field blank to allow forwarding all events.
Request headers
You can add additional headers that will be sent along with the POST request to your endpoint. A typical example is adding an Authentication header with a token that authenticates the request according to your endpoint's rules.
The Content-Type header will always be sent along with the request since the payload itself will always be a valid JSON object.
Example:
Authentication
Bearer 1234567890abcdef1234567890abcdef
To prevent random traffic from generating invalid requests or sending fraudulent events, we recommend setting up an authentication mechanism, such as the token example above, to protect your system from malicious actors.
Last updated
Was this helpful?

