Skip to main content

Overview

Webhook notifications enable real-time communication between Pixel Patrol and your application. Get instant updates on moderation decisions, system events, and more with our reliable webhook delivery system.

Webhook System

Architecture

Key Features

Reliable Delivery

  • Automatic retries with exponential backoff
  • At-least-once delivery guarantee
  • Dead letter queue for failed deliveries

Security

  • HMAC-SHA256 signature verification
  • TLS/SSL required endpoints
  • IP allowlisting support

Performance

  • Sub-second delivery times
  • Parallel processing
  • Rate limiting protection

Monitoring

  • Detailed delivery logs
  • Success/failure metrics
  • Latency tracking

Event Types

Available Events

Implementation

Webhook Endpoint

Your webhook endpoint should:

Signature Verification

Delivery & Reliability

Retry Strategy

Failed webhooks are retried with exponential backoff:

Failure Scenarios

Webhooks are considered failed when:
  • HTTP status code is not 2xx
  • Connection timeout (30 seconds)
  • SSL/TLS errors
  • DNS resolution failures

Dead Letter Queue

After all retries fail:
  1. Event moved to dead letter queue
  2. Admin notification sent
  3. Manual retry available
  4. 30-day retention

Advanced Features

Batch Webhooks

Receive multiple events in one request:

Webhook Filters

Configure which events to receive:

Custom Headers

Add custom headers to webhook requests:

Monitoring & Debugging

Webhook Logs

Detailed logs for each delivery attempt:

Health Monitoring

Track webhook health metrics:
  • Success Rate: Percentage of successful deliveries
  • Average Latency: Time to deliver
  • Queue Depth: Pending webhooks
  • Error Rate: Failed delivery percentage

Testing Tools

Test Endpoint

Send test webhooks to verify setup

Webhook Inspector

View recent deliveries and payloads

Replay Events

Resend historical events

Mock Server

Test against simulated endpoints

Best Practices

Endpoint Implementation

  1. Quick Response: Return 200 immediately
  2. Async Processing: Use queues for heavy work
  3. Idempotency: Handle duplicate events
  4. Error Handling: Graceful failure recovery

Security

  1. Always Verify: Check signatures on every request
  2. Use HTTPS: Never use plain HTTP
  3. Validate Payloads: Sanitize input data
  4. Rate Limit: Protect against floods

Reliability

  1. Handle Retries: Expect duplicate deliveries
  2. Monitor Health: Track success rates
  3. Plan for Failures: Implement fallbacks
  4. Keep Logs: Retain for debugging

Troubleshooting

Common Issues

Debug Checklist

  • Endpoint returns 2xx status
  • Signature verification working
  • SSL certificate valid
  • No firewall blocking
  • Correct event types selected
  • Webhook enabled in settings

Integration Examples

Node.js/Express

Python/Flask