Webhooks
Push events to any system
Send signed events to your other systems the moment records change.
What it is
Event webhooks send a signed HTTP request to your endpoint whenever something happens in your workspace, such as a record being created or updated. Use them to keep other tools in sync without polling.
Webhook developer docsWhat you get
- Subscribe each endpoint to the events it needs
- Every request is signed so you can verify it came from Scratchboard
- Failed deliveries are retried automatically
- Delivery log with status, response code and timing
- Send a test event, retry a failed delivery, roll the signing secret
- Call external APIs from workflows with saved API connections
How it works
Three steps from setup to results.
Add an endpoint
Enter your URL and pick the events to subscribe to.
Verify the signature
Check the signature header with your signing secret before trusting a request.
Monitor deliveries
See every attempt, retry failures and send test events from the endpoint page.
Key capabilities
The core of Webhooks.
Event subscriptions
Choose exactly which events each endpoint receives.
Signed requests
Signature with a timestamp, so receivers can reject old or forged calls.
Automatic retries
Failed deliveries are retried; you can also retry by hand.
Delivery log
Status, response and timing for every attempt.
Frequently asked questions
Short answers to common questions.
What is a webhook?
An HTTP request Scratchboard sends to your server when something happens, so your system hears about changes right away instead of asking repeatedly.
How do I know a request is genuine?
Each request carries a signature made with your endpoint's secret. Your server recomputes it and rejects anything that does not match.
Can I receive data into Scratchboard too?
Yes. Inbound webhooks are part of Integrations, and the REST API accepts writes with an API key.
Related features
These work hand in hand with this one.
Build your first app today.
Start your 7-day free trial, or talk to us about your use case.