account.deletion_requested
A user has submitted an account deletion request (soft-delete). Subscribers mark local user records with deletion_requested_at and notify their local operators — they do NOT auto-delete data. Actual anonymization is gated behind a separate 'account.deletion_approved' event (Phase 4).
Senders
camino
Receivers
colectiva
Data schema
Each field maps to a type hint. | null indicates an optional field.
json
{
"userId": "string",
"orgId": "string | null",
"requestedAt": "string (ISO datetime)",
"emailHash": "string (sha256 hex)",
"source": "string (AppSlug)",
"blockersPassed": "string[]",
"blockersWarned": "string[]"
}Example payload
The following is a synthetic payload that matches the schema. Production payloads are signed with HMAC-SHA256 and delivered to each receiver's registered webhook endpoint.
json
{
"userId": "example-userId",
"orgId": "example-orgId",
"requestedAt": "2026-04-17T12:00:00.000Z",
"emailHash": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"source": "example-source",
"blockersPassed": [
"example-blockersPassed"
],
"blockersWarned": [
"example-blockersWarned"
]
}See also
Generated from ecosystem-sdk/packages/mcp-server/src/registry/events.json. Do not edit by hand.