Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion src/content/docs/build/webhooks.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,8 @@ Three headers come with it:
| `webhook-signature` | `v1,<base64 HMAC-SHA256>`, or two of them separated by a space while a secret rotates |

`data` carries identifiers and the few fields a receiver acts on. It never carries an IP address,
user agent or free-form metadata; those stay in the audit log. The schemas are
user agent or free-form metadata; those go to the audit log and your SIEM (see
[How To Stream Audit Events To A SIEM](/operate/stream-audit-events-siem)). The schemas are
`WebhookEventSchema` and its parts in `@seamless-auth/types` 0.39.0 (`webhook` module).

---
Expand Down Expand Up @@ -761,6 +762,8 @@ once, so a receiver still holding only that one starts failing. The CLI asks bef

- [How To Use Login Hooks And Custom Claims](/build/login-hooks-custom-claims), which are signed the
same way
- [How To Stream Audit Events To A SIEM](/operate/stream-audit-events-siem), for every audit event
with its network detail
- [Auth Events and Auditing](/understand/authevents)
- [How To Use TOTP And Step-Up](/build/totp-step-up)
- [Server SDKs](/build/server-sdks)
Expand Down
Loading