Notification Endpoints

A notification endpoint is a URL that can accept CAP 1.2 formatted XML. This public standard is documented here:

https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2.html

You must have a system which is capable of sending the CAP 1.2 formatted XML in an HTTP request body to use this feature.

Creating a Notification Endpoint

Click the “Create Notification Endpoint” to begin the process:

This will display the Create Endpoint interface:

Fill in the items as follows:

1. Endpoint Name: Give your endpoint a name that is descriptive and will help you quickly identify it later.

2. Status: Set the status of your endpoint to “Enabled”. Later, you may wish to make changes to the endpoint and adjusting the status to “disabled” is quicker than deleting and re-creating the endpoint.

3. Username: You can optionally provide a username for the endpoint. The username and password will need to be supplied in the HTTP header using the “Basic” authentication scheme. See RFC7235 for details: https://tools.ietf.org/html/rfc7617

4. Password: The basic authentication password.

5. Auto-Send to Profile: The Sending Profile(s) that the notification should be automatically sent to. We strongly recommend testing with a profile that contains only a few designated testing recipients before enabling with a production sending profile.

6. Create Notification Endpoint: Click to create the endpoint.

Your endpoint URL will be displayed in the Notification Endpoints listing. Copy the URL and use it in your Requests: