Skip to content
Laritor Documentation

Webhooks

Laritor supports custom webhook integrations to deliver alert data to any external system or service that accepts POST requests. This is ideal for routing alerts to your own APIs, internal tools, or third-party platforms not natively integrated with Laritor.

🔧 How to Integrate Webhooks

Section titled “🔧 How to Integrate Webhooks”

  1. Open Settings

    • Click your profile dropdown in the top-right corner of the dashboard.
    • Select Settings from the dropdown.

  2. Add a Webhook

    • On the Settings page, go to the Webhooks section.
    • Enter a name for the webhook so you can identify it later.
    • Paste the webhook URL that should receive Laritor payloads.

  3. Save the Webhook

    • Save the webhook after entering the name and URL.
    • You can add as many webhook URLs as needed.

📣 Using Webhooks in Alerts

Section titled “📣 Using Webhooks in Alerts”

Once you have added one or more webhooks in Settings, you can select them from the Alerts page.

  1. Go to Alerts

    • Click Alerts in the main navigation menu.

  2. Select a Webhook

    • Under Alerts, choose the webhook you previously added in Settings.

  3. Save Your Alert Configuration

    • Save your alert settings after selecting the appropriate webhook.
    • Laritor will send webhook requests to the selected endpoint whenever the alert is triggered.

🔄 How Laritor Sends Webhooks

Section titled “🔄 How Laritor Sends Webhooks”
  • Method: POST
  • Content-Type: application/json
  • User-Agent: laritor-bot
  • Payload Format: JSON (see below)

📦 Payload Structure

Section titled “📦 Payload Structure”

Laritor sends a JSON payload with the following base fields:

{
  "application_id": "application id",
  "application": "application name",
  "environment_id": "environment id",
  "environment": "environment name",
  "exception": "exception message",
  "exception_class": "exception class",
  "exception_id": "exception id",
  "file": "file path",
  "line": 42,
  "first_occurred_at": "2026-03-31T10:00:00Z",
  "last_occurred_at": "2026-03-31T10:05:00Z",
  "total_occurrences": 12,
  "code": "code snippet where the exception occurred",
  "occurrence_type": "request",
  "exception_url": "https://app.laritor.com/...",
  "occurrence_url": "https://app.laritor.com/..."
}

Field details:

  • application_id
  • application
  • environment_id
  • environment
  • exception
  • exception_class
  • exception_id
  • file
  • line
  • first_occurred_at
  • last_occurred_at
  • total_occurrences
  • code
  • occurrence_type: one of request, command, job, or scheduled_task
  • exception_url
  • occurrence_url

Laritor also includes additional fields based on the occurrence_type:

  • request
    • url
    • request_headers
    • request_body
    • user_id
    • user_name
    • user_agent
    • user_ip
  • command
    • command
  • job
    • job
  • scheduled_task
    • scheduled_task

🧪 Example Payload

Section titled “🧪 Example Payload”
{
  "application_id": "1",
  "application": "Weather API",
  "environment_id": "1",
  "environment": "production",
  "exception": "Call to undefined function App\\\\Services\\\\foo()",
  "exception_class": "Error",
  "exception_id": "1",
  "file": "/var/www/app/Services/ReportService.php",
  "line": 78,
  "first_occurred_at": "2026-03-31T10:00:00Z",
  "last_occurred_at": "2026-03-31T10:05:00Z",
  "total_occurrences": 54,
  "code": "return foo($payload);",
  "occurrence_type": "request",
  "exception_url": "https://app.laritor.com/applications/1/environments/1/exceptions/1",
  "occurrence_url": "https://app.laritor.com/applications/1/environments/1/requests/15",
  "url": "https://api.example.com/reports/daily",
  "request_headers": {
    "accept": "application/json",
    "content-type": "application/json"
  },
  "request_body": {
    "report_id": 42
  },
  "user_id": "15",
  "user_name": "Taylor Smith",
  "user_agent": "Mozilla/5.0",
  "user_ip": "203.0.113.10"
}

💡 Use Cases

Section titled “💡 Use Cases”
  • Integrate with PagerDuty or your custom incident system
  • Log alerts to your internal analytics platform
  • Trigger CI/CD pipelines, feature flags, or rollback tools
  • Feed alerts into dashboards or custom UI components