← Spec Hub | Category: Developer APIs
Developer documentation for integrating Baserow ➔ Supabase Webhook Pipeline Specification webhooks into backend applications. Secure your endpoint with HMAC signature checking and payload validation.
Supported Events: resource.created resource.updated resource.deleted event.triggered
Security validation specs for Baserow ➔ Supabase Webhook Pipeline Specification endpoints:
X-Webhook-Signature-256: sha256=e39948eb5499ef4264f548a2502547ae
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_baserow-to-supabase.html_76367",
"event": "resource.created",
"created_at": 1789764045,
"data": {
"resource_id": "res_382",
"status": "active"
}
}
curl -X POST https://your-domain.com/webhook/baserow-to-supabase.html \
-H "Content-Type: application/json" \
-H "X-Webhook-Signature-256: sha256=e39948eb5499ef4264f548a2502547ae" \
-d '{"id": "evt_baserow-to-supabase.html_76367", "event": "resource.created", "created_at": 1789764045, "data": {"resource_id": "res_382", "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.
Your endpoint must return an HTTP 2xx response within 2000ms. Offload heavy processing (email, DB writes) to an asynchronous task queue.
Your framework might be auto-parsing JSON. HMAC generation requires the exact raw byte buffer of the request body before JSON middleware alters keys or spacing.
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.