API Documentation
Technical reference for integrating with Cynteo Alert Bridge.
Webhook Endpoint
Alert Bridge provides a secure webhook endpoint that accepts Azure Monitor alerts.
Endpoint URL
After deployment, a unique webhook URL is generated for your instance. This URL is:
- Automatically configured in your Action Groups during setup
- Protected with signature-based authentication
- Unique to your deployment
π Security: The webhook URL contains authentication tokens and should be kept confidential.
Request Format
Headers
POST /workflows/{id}/triggers/manual/paths/invoke HTTP/1.1
Host: prod-XX.region.logic.azure.com
Content-Type: application/json
User-Agent: Azure-Alerts/1.0
Body
Alert Bridge expects Azure Monitor Common Alert Schema:
{
"schemaId": "azureMonitorCommonAlertSchema",
"data": {
"essentials": {
"alertId": "string",
"alertRule": "string",
"severity": "Sev0|Sev1|Sev2|Sev3|Sev4",
"signalType": "Metric|Log|Activity Log",
"monitorCondition": "Fired|Resolved",
"monitoringService": "string",
"alertTargetIDs": ["string"],
"originAlertId": "string",
"firedDateTime": "ISO8601 string",
"resolvedDateTime": "ISO8601 string",
"description": "string"
},
"alertContext": {
// Alert type specific context
}
}
}
See Alert Schema Reference for complete details.
Response Format
Success Response
HTTP/1.1 202 Accepted
Content-Type: application/json
{
"status": "accepted",
"incidentId": "12345",
"incidentNumber": "INC-001234",
"action": "created|updated",
"timestamp": "2025-10-29T10:00:00Z"
}
Error Responses
400 Bad Request
{
"error": {
"code": "InvalidSchema",
"message": "Alert schema validation failed",
"details": "Missing required field: alertRule"
}
}
401 Unauthorized
{
"error": {
"code": "InvalidSignature",
"message": "Request signature validation failed"
}
}
500 Internal Server Error
{
"error": {
"code": "SolarWindsError",
"message": "Failed to create incident in SolarWinds",
"details": "API returned 401 Unauthorized"
}
}
Rate Limits
Azure Logic Apps Limits
| Tier | Requests/Min | Requests/Day |
|---|---|---|
| Consumption | 60 | 86,400 |
| Standard | 600 | Unlimited |
SolarWinds API Limits
| Tier | Requests/Hour |
|---|---|
| Free | 100 |
| Standard | 1,000 |
| Premium | 5,000 |
Note: Alert Bridge automatically queues requests to stay within limits.
Testing the Integration
Using Azure Action Group Test
The easiest way to test Alert Bridge:
- Go to Azure Portal β Monitor β Action groups
- Select your action group
- Click “Test”
- Select the webhook action
- Click “Test”
- Check SolarWinds for the test incident
Using Azure Alerts
Fire a real alert to test end-to-end functionality:
- Create a test alert rule with easy-to-trigger conditions
- Wait for the alert to fire
- Verify incident appears in SolarWinds
- Check that all fields are populated correctly
Integration Security
Webhook Authentication
- Each deployment has a unique, signed webhook URL
- Authentication is handled automatically
- URLs contain time-limited signatures
Best Practices
- Keep webhook URLs confidential - treat them like passwords
- Use Azure Action Groups - don’t share webhook URLs externally
- Monitor for unauthorized access - review execution logs regularly
Monitoring Integration Health
Check Processing Status
You can monitor Alert Bridge processing through Azure:
- Azure Portal β Your Alert Bridge resource
- View Run History to see recent alert processing
- Check for any failures or errors
- Review execution times
Common Status Indicators
- β Succeeded - Alert processed and incident created/updated
- β οΈ Failed - Error occurred (check details)
- βΈοΈ Skipped - Alert filtered (by severity or other rules)
See Also
- Alert Schema - Input format details
- Incident Fields - Output format
- Configure Action Groups - Setup guide
Questions? Contact support@cynteocloud.com