01
HMAC-signed payloads
Requests carry X-GNS-Timestamp and X-GNS-Signature headers. Verify the HMAC-SHA256 signature and timestamp in your receiver before accepting an event.
OUTBOUND WEBHOOKS
Webhook API for signed application events.
Send event payloads to a public HTTPS endpoint with HMAC signatures, destination validation, and configurable retries.
- Signature
- HMAC-SHA256 (v1)
- Transport
- HTTPS only
- Timeout
- Configurable, 10s default
- Redirects
- Blocked
What the Webhook engine handles for you
02
Validate the destination
The adapter requires public HTTPS destinations, rejects private and local addresses after DNS resolution, and does not follow redirects.
03
Handle retries safely
Rate limits and server errors are retryable under the configured policy. Make your receiver idempotent because delivery retries can repeat a request.
04
Inspect failed requests
Timeouts and receiver errors appear in delivery activity. Investigate or replay exhausted deliveries with the appropriate console permissions.
Webhook · request
POST /api/v1/notifications
Authorization: Bearer <SENDRIN_API_KEY>
Content-Type: application/json
Idempotency-Key: order-4821-shipped
{
"event_key": "order.shipped",
"channel": "webhook",
"recipient": { "url": "https://hooks.example.com/orders" },
"data": { "order_id": "4821" }
}Supported providers
- Any public HTTPS endpoint
Publish an event template and configure the webhook provider with a signing secret. Your public HTTPS receiver must verify signatures, reject stale timestamps, and safely handle duplicate events.
More in App & Integrations
INSTANT DEPLOYMENT
Send your systems events they can verify.
One API, every channel, full delivery visibility. Start free, no credit card required.