| name | faundit-webhooks |
| description | Receive and verify Faundit webhooks. Use when setting up Faundit lost-and-found / returns webhook handlers, debugging signature verification, or handling the item-status and request-status events (statuses like delivered, finished, expired).
|
| license | MIT |
| metadata | {"author":"hookdeck","version":"0.1.0","repository":"https://github.com/hookdeck/webhook-skills"} |
Faundit Webhooks
When to Use This Skill
- Setting up Faundit webhook handlers
- Debugging Faundit signature verification failures
- Understanding Faundit event types (
item-status, request-status) and payloads
- Handling lost-and-found item and request status changes (delivered, finished, expired, etc.)
Verification (core)
Faundit signs each webhook with HMAC-SHA256 (hex) and delivers two headers you care about:
X-Faundit-Signature-Next — current (v1) scheme, signs v1:<timestamp>:<body> (payload integrity). Prefer this.
X-Faundit-Timestamp — the timestamp used in the signed string.
X-Faundit-Signature — deprecated (v0) scheme, signs v0:<timestamp> only (no body integrity). Avoid.
There is no official Faundit SDK — verify manually. Use the request body (before ), and build the signed string as + the value + + raw body.