Skip to content

Notifications – Webhooks Log

The Webhooks Log provides delivery-level visibility for all notification attempts.

Each delivery attempt is recorded independently and is immutable.

Entry Point

The Webhooks Log is accessed from:

Data Exchange → Notifications → Webhooks Log

Tracked Data

Each log entry contains:

  • Webhook name
  • Event name
  • Target URL
  • Delivery timestamp
  • Delivery status
  • HTTP response code
  • Attempt number
  • Payload hash
  • Response body (if present)
  • Error message (if present)

Delivery States

Each attempt is recorded in exactly one of the following states:

  • Delivered
    HTTP 200 received from the target system.

  • Failed
    Any non-200 response or network failure.

  • Retrying
    A previous failure exists and another attempt is scheduled.

Retry Visibility

  • Every retry appears as a new log entry
  • All attempts reference the same:
  • Webhook
  • Event
  • Payload

This allows full inspection of:

  • Initial failure cause
  • Subsequent retry outcomes
  • Final delivery resolution

Payload Inspection

Each log entry exposes:

  • The exact JSON payload that was sent
  • All authentication headers
  • All Minyu-specific headers

Operational Use

The Webhooks Log is used for:

  • Verifying that external systems received events
  • Debugging authentication failures
  • Debugging network and SSL issues
  • Auditing external synchronization
  • Diagnosing duplicate processing