Prerequisites
- A running SnackBase instance
- At least one collection with data
- An external HTTPS endpoint to receive webhooks (for production)
Setup
Store the Signing Secret
Store the returned secret in your server’s environment variables:Never hardcode the secret in your source code.
Implement Signature Verification
Every webhook delivery includes an
X-SnackBase-Signature header. Verify it on your server:- Node.js
- Python
Adding Filters
Only fire webhooks when specific conditions are met:Troubleshooting
Webhook deliveries are failing
Webhook deliveries are failing
Check the delivery history for error details. Common causes:
- Your endpoint is returning non-2xx status codes
- Your endpoint is taking longer than 30 seconds to respond
- DNS resolution is failing for your URL
Signature verification fails
Signature verification fails
Ensure you’re verifying against the raw request body (bytes), not a parsed/re-serialized JSON object. The signature is computed over the exact bytes sent.
Webhook not firing
Webhook not firing
- Verify the webhook is
enabled - Check that the event type matches (
create,update,delete) - If using a filter, verify the expression matches your record data
- Filters that fail to evaluate will still fire the webhook (fail-open)
HTTPS required error
HTTPS required error
In production, SnackBase requires HTTPS URLs. For local development, HTTP is allowed. Private IPs (localhost, 10.x, 192.168.x) are also blocked in production.
Next Steps
- Outbound Webhooks Concept — full reference
- Webhooks API Reference — all endpoints
- Webhooks SDK Reference — SDK methods