← Spec Hub | Category: CRM & SaaS
Comprehensive specification for handling incoming Notion API ➔ Vectorizer.AI Webhook Pipeline Specification webhook events. This reference covers cryptographic payload verification, request headers, and retry protocols.
Supported Events: contact.creation deal.stage_change company.updated ticket.created
Security validation specs for Notion API ➔ Vectorizer.AI Webhook Pipeline Specification endpoints:
X-Webhook-Signature-256: sha256=888843d3d9a6f01418831720ff40273b
const crypto = require('crypto');
const expected = crypto.createHmac('sha256', secret).update(rawBody).digest('hex');
const isValid = crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(signature));
import hmac, hashlib
expected = hmac.new(secret.encode(), raw_body, hashlib.sha256).hexdigest()
is_valid = hmac.compare_digest(expected, incoming_sig)
{
"id": "evt_notion-to-vectorizer.html_11589",
"event": "contact.creation",
"created_at": 1789764056,
"data": {
"resource_id": "res_900",
"status": "active"
}
}
curl -X POST https://your-domain.com/webhook/notion-to-vectorizer.html \
-H "Content-Type: application/json" \
-H "X-Webhook-Signature-256: sha256=888843d3d9a6f01418831720ff40273b" \
-d '{"id": "evt_notion-to-vectorizer.html_11589", "event": "contact.creation", "created_at": 1789764056, "data": {"resource_id": "res_900", "status": "active"}}'
| Status Code | Status Meaning | Integration Action |
|---|---|---|
200 OK | Success | Event payload validated and queued. |
400 Bad Request | Malformed Payload | Check payload structure and JSON formatting. |
401 Unauthorized | Signature Mismatch | Verify secret key and digest computation. |
500 Error | Server Error | Triggers provider automated retry backoff. |
Always process incoming events asynchronously using a message queue. Never perform long-running DB queries or external API calls synchronously within the HTTP response handler.
Failed deliveries (non-2xx responses) trigger an exponential backoff retry schedule over a period ranging from 24 to 72 hours.
Compute the HMAC SHA-256 hash on the raw request body using your shared secret and compare it against the incoming signature header using time-constant comparison.
While signature verification is primary, restricting traffic to published origin IP ranges adds a robust layer of perimeter security.