BugSplat’s Webhook integration allows your team to configure custom notifications for each new report or group of reports. BugSplat's Webhook integration allows you to build integrations unique and novel integrations that can be tailor-fit to your company's workflow.
- Login to BugSplat and navigate to the Notifications page.
- Select the Database for which you'd like to configure alerts.
- Under the Webhook section, enter the URL of the webhook you would like to invoke and click Update.
- Use the toggle buttons to set your notification preferences. You can be notified for each new report or unique report group.
Once configured, BugSplat will post an object that matches the following interface to your Webhook. Unlike other notifications, Webhook crash notifications have no maximum throughput limitation.
POST https://your-domain.com/path/to/your/webhook
Notification payload for new BugSplat report or new BugSplat group
| Name | Type | Description |
|---|---|---|
| id | number | BugSplat ID for new report |
| crashTypeId | number | Enum representing platform used to post report |
| parentStackKeyId | string | BugSplat ID for report group before grouping rules were applied |
| stackKeyId | number | BugSplat ID for report group |
| newStackKeyId | boolean | True if this is the first occurence of stackKeyId |
| stackKeyName | string | Function name and line number used to group the report |
| stackId | number | Unique call stack identifier |
| newStackId | boolean | True if this is the first occurence of stackId |
| database | string | BugSplat database where report is stored |
| application | string | Application name associated with report |
| version | string | Versions associated with report |
| key | string | Identifier for specific flavor of application associated with report |
| user | string | End-user associated with generated report |
| string | End-user's email associated with generated report | |
| ipAddress | string | End-user's IP address (can be obfuscated via Options page) |
| mfa | string | Hash representing report call stack |
| exceptionCode | string | Code associated with issue that caused the report to be generated |
| exceptionMessage | string | Message associated with issue that caused the report to be generated |
| received | datetime | Time-stamp of generated report |
| reportXml | string | XML doc representing the fully processed BugSplat report |
| debugOutput | string | Output generated when running the debugger |