Webhooks & events
Register an endpoint and Jetwild POSTs a signed JSON event to it when something happens — so you can react instead of poll.
You can register webhooks, rotate their signing secret, and send a test
delivery today. Automatic event emission (the catalog below) is
coming soon — right now only the manual test ping fires. Build your
receiver + signature check now; events will start arriving when emission ships.
Register a webhook
Manage webhooks in Settings → Developers (an OWNER or DIRECTOR of the workspace).
Each webhook gets a signing secret prefixed whsec_, shown once.
Events
The event catalog Jetwild will emit. Coming soon
Payload
Every delivery is a JSON body with the event name and its data, plus an
x-jetwild-event header naming the event.
Verify signatures
Every request carries an x-jetwild-signature header of the form
t={timestamp},v1={signature}, where signature is
HMAC-SHA256(secret, "{timestamp}.{rawBody}") as hex. Recompute it over the raw
request body and compare before trusting the payload.
Compute the HMAC over the exact bytes you received, before any JSON parsing — re-serializing can change whitespace and break the signature.
Retries
Failed deliveries retry up to 5 times with exponential backoff (starting at 2s). After 10 consecutive failures a webhook is automatically disabled — re-enable it in Settings once your endpoint is healthy.