Webhooks
Receive real-time notifications when contracts change state
Webhooks let your server react to events on the Vlens platform in real time, without polling. When an event occurs, Vlens sends an HTTP POST with a JSON payload to a URL you configure in the Vlens portal.
Use cases
Webhooks support:
- Tracking contract lifecycle changes (creation, approval, signing, countersignature)
- Synchronizing contract status with external systems
- Triggering automated workflows on contract events
- Maintaining audit and monitoring dashboards
Available events
Setting up a subscription
- Sign in to the Vlens portal
- Navigate to Webhook Subscriptions
- Click Add New Webhook Subscription
- Provide:
- Webhook Endpoint — the URL that will receive
POSTnotifications - Webhook Events — one or more events to subscribe to
- Webhook Endpoint — the URL that will receive
- Click Save
Subscriptions are event-specific and endpoint-specific — multiple subscriptions can target the same event with different endpoints (useful for fan-out to different downstream systems).
Payload format
Every webhook delivery is a POST with a JSON body:
Data for BusinessRequestStatusChange
Verifying webhook signatures
Vlens signs every delivery with an HMAC-SHA256 hash of the raw request body, sent in the abp-webhook-signature header. Always verify this signature before processing the payload.
How to verify:
- Read the raw request body (before JSON parsing)
- Compute
HMAC-SHA256(rawBody, webhookSecret) - Compare your digest (hex-encoded) to the value after
sha256=in the header - Reject the request if they do not match
Never process a webhook without verifying the signature. An unverified endpoint can be spoofed by anyone who knows your URL.
JavaScript
Python
cURL test
Your webhook secret is configured when you create the subscription in the Vlens portal. Store it in an environment variable — never in source code.
Receiving a webhook (without signature verification)
The example below skips signature verification. Use only for local development — always verify in production.
Delivery logs
Every webhook delivery is logged and viewable in the Vlens portal. Each log entry includes:
- HTTP method (
POST) - Source IP address
- Timestamp
- Request headers
- Request body
Use the delivery log to debug failed or unexpected deliveries.
Common patterns
Reconcile on completion
Polling fallback
For mission-critical workflows, combine webhooks with periodic polling of
GET /api/BusinessRequest/CurrentListIds to catch any missed deliveries.

