Overview
When a user opens a magic link and CIP data is incomplete, RaaS Widgets can send auser.data_request webhook. You then fulfill the gaps with PUT /partner/data-requests/:id before the widget asks the user.
Data requests are non-blocking. Acknowledge the webhook quickly, fetch data, then call the reply endpoint. If you respond before the user reaches CIP, they often skip data entry.
Webhook payload
Webhook authenticity headers:
X-RAAS-Signature, X-RAAS-Timestamp, and X-RAAS-Event. Verify them as documented in Webhook security.
Configure your HTTPS endpoint and copy the webhook secret in the Partner Portal (Settings → Webhooks).
Fulfill the request
string
required
Must match the webhook
data.referenceId.object
required
Only the fields you can provide — partial responses still reduce friction.
Success
Common errors
Handler sketch
Store your webhook secret as an env var (example name):Next steps
User data
Friction vs prefills.
Webhook security
HMAC verification with legacy header names.