AlertMedia

Authentication & Authorization

Credentials

• AlertMedia uses token-based authentication, allowing users to authenticate API requests by inputting their tokens into the HTTP authorization bearer token header.
• API Admin Token can be obtained from the AlertMedia Company Settings (see AlertMedia Connection Instructions ).
• Publicly exposing your API credentials can allow unauthorized access to the AlertMedia API endpoints, and your AlertMedia data by a third party. DataGrail stores your API credentials encrypted and protected.

Base URL

The base URL dependents on the customer’s AlertMedia sub-domain:

• https://yourdomain.alertmedia.com/api

Endpoints Utilized

Validate that credentials are good based on a successful response:

• GET {BASE_URL}/login

Limits

The AlertMedia API is throttled to 100 requests per second and is subject to change in the future. All requests over the rate limit will fail with a 429 error and not be saved by AlertMedia.

DataGrail processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).

Access

For an access request, DataGrail will take the following actions:

• Search users by the Data Subject multiple identifiers: email and phone.
• For all objects found, DataGrail will return all available fields. You can edit which objects and fields you want to provide to the Data Subject via our Portal Requests.

Endpoints Utilized

• GET {BASE_URL}/users

note

DataGrail also supports the Direct Contact Access workflow for AlertMedia.

Deletion

For a deletion request, DataGrail will take the following actions:

• Search users by the Data Subject multiple identifiers: email and phone.
• Unsubscribe the user from all from communications channels.
• Delete the user.

Endpoints Utilized

• GET {BASE_URL}/users
• POST {BASE_URL}/users/{user_id}/unsubscribe
• DELETE {BASE_URL}/users/{user_id}

note

DataGrail also supports the Direct Contact Deletion workflow for AlertMedia.