Webhook Common Questions
Question | Answer |
|---|---|
Does the profile webhook lifecycle diagram mean webhooks only fire on status change? | No. profile.updated also fires for some metadata changes (e.g. customer_reference, assignee) without review_status changing. The diagram shows the main lifecycle moments, not every trigger. In-progress portal work and adding a person via API often do not fire Status Webhooks until submit or a later step. See When profile.updated fires below. |
Can we subscribe to specific statuses only? | No. You cannot filter by status in the dashboard. Enable the Status Webhook once; your handler filters on data.review_status. Use early events (profile.created / profile.updated with Processed) for parallel sales or operations work while due diligence continues. |
What fires when a business or individual is added or changed? | Business: profile.created on case create; profile.updated on status and metadata changes. Adding a person (POST /representatives) does not webhook by itself. |
Is the webhook payload enough for CRM? | No. Use the webhook as a trigger, then GET endpoints for full data. |