Configure a custom endpoint to send notifications to your preferred apps, even if they aren’t on the list of preconfigured options.

Custom endpoints offer the advantage of allowing you to customize the message body too.

To add a custom endpoint

Add the endpoint

To add a new custom endpoint, click Add endpoint. Specify the URL, method, and headers. For POST/PUT methods, you can configure the message body, if relevant.

Ports & security considerations

Alerts can only be sent on ports 80 & 443. If you accidently set a custom port for an alert endpoint, the alert will not be sent.

It is best to avoid opening a port in your firewall to allow access for custom endpoints. This is because the IP range is used by all customers and should be treated with caution.

If you decide to open a port on your firewall for a custom endpoint, follow these best practices:

  • Make sure to add a verification token in the JSON payload of the custom endpoint and verify that the token exists on the receiving end.
  • Allow external access only to this specific endpoint.

Here’s an example of a JSON payload for an alert that includes a verification token:

"token": "<SomeSecurityToken>",
"alert_title": "<alert_title>",
"alert_description": "<alert_description>",
"alert_severity": "<alert_severity>",
"alert_event_samples": "<alert_samples>"
Test the endpoint

Click Run the test to test your endpoint. shows if the message was successfully sent.

Check that the endpoint received the message.

This is not required, but highly recommended.

Save the endpoint

Click Save to save your endpoint.

Configure a custom endpoint