Our alerting solution is centered around two concepts: events and channels. The occurrence of an event can be configured to trigger an alert. A channel describes the delivery method for an alert. Every configured alert consists of an event type / channel pair. This level of granularity allows alerting to be configured to your exact preference.
Alerts (0.0.1)
Download OpenAPI description
Languages
Servers
US Mailgun
https://api.mailgun.net/
EU Mailgun
https://api.eu.mailgun.net/
- US Mailgun
https://api.mailgun.net/v1/alerts/settings/slack
- EU Mailgun
https://api.eu.mailgun.net/v1/alerts/settings/slack
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X PUT \
-u <username>:<password> \
https://api.mailgun.net/v1/alerts/settings/slack \
-H 'Content-Type: application/json' \
-d '{
"token": "string",
"team_id": "string",
"team_name": "string",
"scope": "string"
}'- US Mailgun
https://api.mailgun.net/v1/alerts/settings/slack
- EU Mailgun
https://api.eu.mailgun.net/v1/alerts/settings/slack
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X DELETE \
-u <username>:<password> \
https://api.mailgun.net/v1/alerts/settings/slack- US Mailgun
https://api.mailgun.net/v1/alerts/settings/webhooks/signing_key
- EU Mailgun
https://api.eu.mailgun.net/v1/alerts/settings/webhooks/signing_key
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X PUT \
-u <username>:<password> \
https://api.mailgun.net/v1/alerts/settings/webhooks/signing_keyResponse
application/json
{ "signing_key": "string" }