Configure webhooks at account.intelliprint.net/api_keys. Powered by Svix for reliable, enterprise-grade event delivery.
Benefits of Webhooks
Instead of constantly polling the API to check print job status:Real-time Updates
Receive instant notifications when events occur
Reduced API Calls
No need to poll for status changes
Scalable
Handle thousands of events reliably
Automatic Retries
Svix automatically retries failed deliveries
Event Types
Intelliprint sends webhooks for the following events:| Event Type | Description | When It Fires |
|---|---|---|
letter.updated | Letter status changed | When a confirmed letter’s status is updated (e.g., waiting_to_print, printing, enclosing, shipping, sent, returned, failed_wrong_address) |
mailing_list.addresses_validated | Address validation completed | When all recipients in a mailing list have been validated |
Each
letter.updated event includes the letter’s current status, allowing you to track the full lifecycle from confirmation through delivery or return.Setting Up Webhooks
1. Access Webhook Settings
Configure webhooks in your Intelliprint account:1
Go to API Settings
Navigate to account.intelliprint.net/api_keys and access the webhooks section.
2
Create Endpoint
Add the URL where you want to receive webhook events:
3
Select Events
Choose which events you want to receive (e.g.,
letter.updated, mailing_list.addresses_validated).4
Test Webhook
Use the built-in testing tools to send test events to your endpoint.
Powered by Svix: Webhook management is handled by Svix, ensuring reliable delivery with automatic retries. You can also access the Svix dashboard directly for advanced features.
2. Create Your Webhook Endpoint
Implement an endpoint in your application to receive webhook events:Event Payload Structure
letter.updated
Fired when a confirmed letter’s status changes:waiting_to_print- Queued for printingprinting- Currently being printedenclosing- Being placed in envelopeshipping- Handed to Royal Mailsent- Dispatchedreturned- Returned to senderfailed_wrong_address- Delivery failed
mailing_list.addresses_validated
Triggered when all recipients in a mailing list have been validated:Webhook Security
Verify Signatures
Svix signs all webhooks with a secret key. Use the Svix SDK to verify:Get Your Webhook Secret
Find your webhook secret in your API settings or in the Svix dashboard under your endpoint settings.Each webhook endpoint has its own unique secret. Keep these secrets secure and never commit them to version control.
Best Practices
1. Return 200 Quickly
Respond with HTTP 200 as quickly as possible, then process the event asynchronously:2. Handle Idempotency
Webhooks may be delivered more than once. Use the event ID to avoid duplicate processing:3. Implement Retry Logic
If your endpoint fails, Svix will automatically retry with exponential backoff. Ensure your endpoint is idempotent to handle retries safely.4. Monitor Webhook Health
Check webhook delivery success rates in your API settings or the Svix dashboard:- Delivery success/failure rates
- Response times
- Error logs
- Retry attempts
5. Use Test Mode
Test your webhook integration using test mode events:Testing Webhooks Locally
Use Built-in Testing
Test webhooks locally using the testing tools or ngrok:- Testing Tools (Recommended)
- ngrok
Use the built-in testing tools:
- Go to account.intelliprint.net/api_keys
- Click “Send Test Event” for your endpoint
- View the request/response in real-time
Troubleshooting
Webhooks Not Receiving Events
Check endpoint URL
Check endpoint URL
Ensure your endpoint is publicly accessible and returns HTTP 200.
Verify signature validation
Verify signature validation
Make sure you’re correctly verifying the Svix signature.
Check webhook logs
Check webhook logs
View detailed delivery logs in your API settings or the Svix dashboard.
Test with testing tools
Test with testing tools
Use the built-in testing tools to send test events to your endpoint.
Common Errors
| Error | Cause | Solution |
|---|---|---|
400 Invalid signature | Signature verification failed | Check webhook secret is correct |
timeout | Endpoint took too long to respond | Return 200 faster, process async |
connection refused | Endpoint not accessible | Check firewall, ensure server is running |
Webhook Management Features
Manage your webhooks at account.intelliprint.net/api_keys:Real-time Logs
View all webhook deliveries and responses
Manual Retry
Manually retry failed deliveries
Event Inspector
Inspect payload and headers
Testing Tools
Send test events to your endpoint
Rate Limits
Webhook delivery is not subject to API rate limits, but your endpoint should be able to handle:- Burst: Up to 100 requests/second during high-volume periods
- Sustained: Average of 10-50 requests/second

