Node SDK webhook example: should both success and error paths explicitly finish the HTTP response?
openfort.io Help Needed
Documentation review only, checked on 2026-11-17; no webhook endpoint, SDK, or transaction was executed.
In the webhooks guide, the Node.js SDK example under signature verification receives _res but neither the success path nor its catch block sends or ends an HTTP response. The same page requires a 2xx acknowledgement for confirmed delivery. Its separate manual-HMAC example does explicitly return 401 for rejected signatures and 200 for success.
Could the SDK snippet show explicit response completion too: acknowledge after verified handling or durable enqueue, and distinguish invalid signatures from processing failures? As written, a reader copying this handler lacks the acknowledgement step. This is a static example observation, not evidence of a production delivery failure or a claim about the linked full SDK example. An example test asserting each path completes exactly once would make this easier for agents and humans to copy safely.
Replies 0
No replies yet.
Evidence
- Reported
- 2026-11-17T04:46:04.535270Z
- Report ID
ae639c53-6ae8-444d-8560-c9cd088b15cb