user.signed_up

A new Better Auth user was provisioned under an agency hierarchy (admin-invoked create or invite flow).

Category: User Lifecycle

Emitted when: After the Better Auth user record commits AND the agency_id is resolvable via the upward managerId walk. Platform-tier users (super_admin / admin) do not fire this event.

Envelope

Every delivery wraps the event-specific data block in the canonical envelope documented on the webhook overview page. The body carries SIX keys; the HMAC signature is delivered as the X-Webhook-Signature request header on the inbound POST to your endpoint (NOT as a body field; including it in the body would make the HMAC a function of its own output).

Field	Type	Description
event_id	string	ULID; globally unique. Safe to persist as the dedup key.
event_type	string	Always user.signed_up for this event.
api_version	string	Payload schema version (YYYY-MM-DD).
timestamp	integer	Unix epoch seconds at dispatch time.
nonce	string	ULID; unique per delivery, used for replay rejection.
data	object	Event-specific payload (see below).

Delivery also sets three HTTP headers on the inbound POST:

Header	Meaning
X-Webhook-Event-Id	Mirrors event_id; cheaper than parsing the body to dedup.
X-Webhook-Timestamp	Mirrors timestamp for replay-window checks.
X-Webhook-Signature	sha256=<hex> HMAC over timestamp.body.

Data schema

Field	Type	Required	Description
agency_id	string	yes	Agency Id
user_id	string	yes	User Id
email	string	yes	Email address used for signup
role	"media_agency" | "team" | "broker" | "agent" | "assistant" | "viewer"	yes	Role
name	string | null	no	Name
signed_up_at	string	yes	Signed Up At
invited_by	string | null	no	Actor token of the creator: 'user:' for dashboard admin-create or 'admin:' for admin-tool/background paths; None when emission path cannot attribute.

Sample payload

The sample below is a live fixture. Feed the exact body bytes shown plus the timestamp into the HMAC-SHA256 recipe from the webhook overview using the documented test-vector secret (test_secret_001 ) and you will recover the signature header value printed below.

Body (delivered as the HTTP request body):

{
  "event_id": "evt_14PKZET7AZG4JK1TFSHQPAY7E7",
  "event_type": "user.signed_up",
  "api_version": "2026-04-17",
  "timestamp": 1745339401,
  "nonce": "51WZMW39CBBC6CRK4NVG5AYTJP",
  "data": {
    "agency_id": "user_01HXAGENCY0000000000000",
    "user_id": "user_01HXAGENCYUSER000000000",
    "email": "user@example.com",
    "role": "agent",
    "name": "Jane Smith",
    "signed_up_at": "2026-05-29T12:00:00Z",
    "invited_by": "user:user_01HXAGENCYOWNER00000000"
  }
}

Signature header (delivered as X-Webhook-Signature on the same request):

sha256=071a28af32615f0e62035daaefd065b8072d9b02a6e50d120799b55b8a192c58

Retry behaviour

Failed deliveries retry on the sequence 2, 4, 8, 16, 32 seconds (five attempts plus the initial call for a total of six over approximately 62 seconds of wall clock). After the final attempt the delivery lands in the dead-letter queue and the dashboard operator can replay it from Settings > API Keys > Webhook Endpoint > Deliveries. See the webhook overview for the full rules.

Verification

Every receiver MUST verify the X-Webhook-Signature header using the recipe in the webhook overview. Rejecting deliveries whose timestamp is more than 5 minutes off your wall clock (after NTP correction on your side) or whose nonce has already been consumed in the last 10 minutes is part of the contract.