Async Notifications

Webhooks & Events

Format, Validate, and Convert JSON Instantly

Configure Webhook Read API Reference

Setup

Trigger automatic callbacks when long-running JSON transformations exceed the standard 15-second timeout window. Ideal for batch processing datasets over 50MB or complex schema migrations.

Navigate to your dashboard at app.jsonify.dev/integrations and paste your secure HTTPS endpoint. JSONify binds each webhook to a unique API key, ensuring only authorized payloads reach your infrastructure. Enable signature verification using your workspace secret to validate the X-Jsonify-Signature header on every incoming request. Your endpoint must respond within 3 seconds or the delivery is marked as pending.

Generate API Key

Payloads

Every webhook delivery contains a standardized JSON envelope. Inspect the event_type field to route logic correctly.

validation_failed

Triggered when the target schema rejects your input. Includes the exact path of the failing node and the expected data type.

{
  "event_type": "validation_failed",
  "job_id": "jb_8842a9f1",
  "timestamp": "2024-05-12T14:30:00Z",
  "error": {
    "path": "$.users[2].contact.email",
    "message": "Expected string, received null",
    "schema_version": "v2.4.1"
  }
}

conversion_complete

Delivered upon successful transformation. Contains a secure download URL valid for 24 hours and byte-level processing metrics.

{
  "event_type": "conversion_complete",
  "job_id": "jb_8842a9f1",
  "timestamp": "2024-05-12T14:32:15Z",
  "result": {
    "download_url": "https://cdn.jsonify.dev/out/jb_8842a9f1.json",
    "input_size_bytes": 14502800,
    "output_size_bytes": 11204500,
    "processing_time_ms": 4200
  }
}

Retry Policy

JSONify automatically handles transient network failures using an exponential backoff strategy to prevent endpoint overload.

If your server responds with a 5xx status or fails to acknowledge the request within 3 seconds, we retry up to 5 times. The intervals follow a 2-minute, 6-minute, 18-minute, and 54-minute progression. After the final attempt, the webhook is marked as dropped and logged in your audit trail. For guaranteed delivery, ensure your endpoint returns a 2xx status code before closing the connection. You can monitor historical delivery attempts and manually trigger redelivery from the Events tab.

View Delivery Logs