Summary
Creators receiving webhook callbacks need to know how to confirm a request actually came from AccessLayer and was not forged by a third party. Without a verification mechanism documented, creators have no way to trust the payload.
Scope
- Document the webhook request signature scheme: which header carries the signature, what is signed (e.g. timestamp + body), and which algorithm is used
- Provide a step-by-step verification guide with a pseudocode example
- Explain the replay attack protection mechanism (e.g. timestamp window)
- Add a note on what to do if signature verification fails: return 400, do not process the payload
Acceptance Criteria
ETA: 12 hours
Coordinate on Telegram
Summary
Creators receiving webhook callbacks need to know how to confirm a request actually came from AccessLayer and was not forged by a third party. Without a verification mechanism documented, creators have no way to trust the payload.
Scope
Acceptance Criteria
ETA: 12 hours
Coordinate on Telegram