How it works
DeepSmith sends events
When a subscribed event fires, DeepSmith sends a signed
POST request to your URL with the event payload.Key features
Signed payloads
Every delivery is signed with HMAC-SHA256 so you can verify it came from DeepSmith.
Automatic retries
Failed deliveries are retried up to 3 times with exponential backoff (10s, 60s, 5min).
Delivery logs
Full audit trail of every delivery attempt including response status, body, and timing.
Auto-disable
Webhooks are automatically disabled after 10 consecutive failures to protect your endpoint.
Supported events
DeepSmith fires webhooks for six event types across your content pipeline:| Event | Description |
|---|---|
content.status_updated | An article’s status changed (e.g., draft to published) |
research_batch.status_updated | A research batch completed or failed |
agent_task.status_updated | An AI agent task changed state |
topic.status_updated | A topic cluster’s stage changed |
iq.status_updated | An IQ analysis completed or changed stage |
sitemap_url.status_updated | Sitemap URL processing completed or failed |
You can subscribe a single webhook to one or more events. Each webhook can listen to any combination of the six event types.
Quick example
Here’s a minimal Node.js server that receives webhook deliveries:Next steps
Create a webhook
Register your first webhook endpoint via the API.
Verify signatures
Learn how to validate webhook signatures in your server.
Event payloads
See the full payload schema for each event type.
Handle deliveries
Understand retry logic, failure handling, and best practices.