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/slack/oauth
- EU Mailgun
https://api.eu.mailgun.net/v1/alerts/slack/oauth
- 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/slack/oauth- US Mailgun
https://api.mailgun.net/v1/alerts/slack/channels/{id}
- EU Mailgun
https://api.eu.mailgun.net/v1/alerts/slack/channels/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
-u <username>:<password> \
'https://api.mailgun.net/v1/alerts/slack/channels/{id}'Response
application/json
{ "id": "C012AB3CD", "name": "general" }
- US Mailgun
https://api.mailgun.net/v1/alerts/slack/channels
- EU Mailgun
https://api.eu.mailgun.net/v1/alerts/slack/channels
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
-u <username>:<password> \
'https://api.mailgun.net/v1/alerts/slack/channels?page=string&limit=0'Response
application/json
{ "items": [ { … } ], "paging": { "first": "https://api.mailgun.net/v1/alerts/slack/channels?page=foo", "next": "https://api.mailgun.net/v1/alerts/slack/channels?page=bar" } }