Setting up Webhook Notifications

URIports can already notify users by email and Telegram, but many teams need notifications that plug directly into their preferred tooling. To support that, URIports now offers webhook notifications. When an issue triggers a notification, URIports sends an HTTP POST with structured JSON to your chosen endpoint, giving your system the data immediately so it can react as needed.

Why Webhooks Are Useful

While email and Telegram remain useful for human-facing notifications, many teams need alerts to flow straight into monitoring stacks, ticketing systems, automation pipelines, or custom integrations. Webhooks provide a clean way to do that: you supply an endpoint, and URIports delivers consistent JSON whenever an notification occurs.

Notification Structure

All webhook notifications follow a standardized structure. Example:

{
    "account": {
        "id": "1337",
        "owner": "info@example.com"
    },
    "webhook": {
        "id": "7b307dfec69f05ef",
        "name": "My Webhook"
    },
    "notification": {
        "id": "01d0f28be445fa7e9ebbea89ae509555",
        "timestamp": "2025-12-08T14:24:50Z",
        "type": "nospf",
        "date": "2025-12-08",
        "title": "No SPF policy found on (sub)domain(s)",
        "domain": "example.com",
        "message": "Received DMARC reports from multiple sources indicate that the following hostname(s) sent out 76,392 messages despite having no SPF policy: example.com",
        "link": "https://app.uriports.com/report/dmarc-rua",
        "moreinfo": "https://www.uriports.com/tools/dmarc-validator"
    }
}

Your endpoint only needs to return HTTP 2xx. URIports automatically retries failed deliveries with exponential backoff.

Customize JSON template

The JSON is fully customizable, allowing you to tailor it to the exact input your endpoint requires. When editing the JSON format, ready-made templates are available for Slack, Microsoft Teams, and Discord. Jira and Confluence work seamlessly with the default JSON template, since you can configure the Jira-side endpoint to map fields according to your requirements.

How to Configure a Webhook

• Open Settings in your URIports account.
• Go to Notifications.
• In the popup, locate the Webhooks section.
• Create a webhook and assign a descriptive name.
• Enter the endpoint URL.
• Add authentication headers as required (e.g., API keys).
• Use Send test notification to verify connectivity.
• Save the webhook.
• Review the event log to inspect delivery attempts and diagnose issues.
• Edit the JSON template to tailor it to your liking.

Idempotent Processing

Each event contains a unique notification.id. Store processed IDs on your side and ignore duplicates. This ensures reliability when retries occur.

Delivery Order

Webhook events are delivered sequentially. A new event is sent only after the previous one has been delivered successfully or marked as failed, ensuring predictable processing order.

Authentication Options

URIports can attach any custom headers you specify. Typical patterns include:

• Custom headers such as X-Apikey: YOUR_KEY
• Authorization headers such as Authorization: Bearer YOUR_KEY or Authorization: Token YOUR_KEY

Your endpoint receives these headers with every request and can validate them before handling the payload.

Final Notes

Webhook support gives teams direct, machine-readable access to URIports alerts, enabling deeper automation and integration. Whether you're feeding events into observability tooling or triggering custom workflows, webhooks provide the flexibility to build exactly what your environment requires.