webhook_id
in the path. This ID is returned when a webhook is created via the Create Webhook endpoint.The request body accepts a flexible JSON payload consisting of arbitrary key-value data. Once submitted, the event will be processed by the webhook engine and evaluated against any matching rulesets to determine whether an incident should be triggered.
Use cases:
- Trigger incidents from external systems — Submit alerts or event payloads from cloud providers, log systems, or internal tools.
- Custom monitoring workflows — Report failures, anomalies, or health checks via automation scripts using a valid webhook ID.
- Payload-driven automation — Drive incident creation logic based on dynamic field values submitted with each event.
Expected Behavior:
- On success, the webhook will process the data and return a confirmation message along with additional meta information such as the IP address and content type.
- If the webhook ID is invalid, an error message will be returned.