Connect APVISO with Webhooks

How APVISO Integrates with Webhooks

APVISO's webhook integration provides raw, real-time event delivery to any HTTP endpoint. For organizations that need to build custom integrations, feed internal systems, or implement unique workflow logic, webhooks offer maximum flexibility with no intermediary platforms.

Real-Time Event Delivery

When APVISO's AI agents discover a vulnerability, a webhook event is fired immediately. The HTTP POST request hits your endpoint within seconds of the finding being confirmed. This real-time delivery is faster than any polling-based integration and ensures your custom systems have the latest security data as soon as it is available.

Event Types

APVISO webhooks deliver several event types. Finding events fire when a vulnerability is discovered and include the full finding data: title, severity, CVSS score, affected endpoint, description, reproduction steps, and remediation guidance. Scan events fire at scan lifecycle milestones: started, progress update, completed, and failed. Report events fire when a scan report is generated and include a download link.

You configure which event types are delivered to each webhook endpoint. One endpoint might receive only finding events while another receives the full event stream.

Payload Structure

Every webhook payload follows a consistent JSON structure with an event field identifying the event type, a timestamp, and a data object containing the event-specific details. This consistent structure simplifies parsing on the receiving end — your webhook handler can dispatch based on the event type and extract details from the data object.

Security and Verification

APVISO signs every webhook delivery with an HMAC-SHA256 hash using your webhook secret. The signature is included in the X-APVISO-Signature header. Your endpoint should verify this signature before processing the payload to confirm the request came from APVISO. This prevents attackers from injecting fake vulnerability data into your systems.

Reliability and Retries

Webhook deliveries are reliable. If your endpoint returns a non-2xx status code or times out, APVISO retries with exponential backoff: 1 minute, 5 minutes, 30 minutes, and 2 hours after the initial failure. Every delivery attempt is logged in APVISO's webhook delivery log, where you can inspect request payloads, response codes, and timing for debugging.

Common Use Cases

Webhooks enable custom integrations that pre-built integrations cannot cover. Common use cases include feeding findings into an internal vulnerability database, triggering custom CI/CD pipeline actions, updating internal risk dashboards, populating data warehouses for security analytics, and integrating with proprietary ticketing or workflow systems. The raw event data gives you complete control over how APVISO findings are processed and routed in your environment.