Webhooks

You can use a generic Webhook target to receive structured notifications from your Memfault Project. Webhooks are triggered by events in your Project, such as new issues being created, or alerts being triggered.

Headers

Webhooks are delivered with the following headers:

• Content-Type

  This is always application/json

• Memfault-Delivery

  A unique identifier per webhook invocation. Retries will have the same Memfault-Delivery value and it can thus be used to deduplicate requests.

• X-Signature-SHA256

  A HMAC-SHA256 Signature of the payload.

  To verify the authenticity of the webhook payload, use the HMAC signing secret generated when you created the target. The Signature is calculated on the raw payload body using SHA256.

  info

  You can find sample code online for various languages to help you verify the Signature.

Payload Format

Webhooks have the following structure:

{
  "type": "<event type>",
  "project": {
    "id": "<project id>",
    "slug": "<project slug>",
  },
  // ... additional data depending on the event type
}

Webhook Event Types

info

Generic Webhooks are experimental and the payloads are subject to change

Event Type
test_notification.dispatched
issue.created
issue.reopened
issue.regressed
issue.resolved
issue_comment.created
device_threshold_alert.summary
device_threshold_alert.incident_started
device_threshold_alert.incident_ended
fleet_threshold_alert.triggered