Webhook event types
"domain.added": Indicates that DNS records have been successfully added.- For Entri Sell, this means the domain has been registered and connected.
- For Entri Connect, it confirms that DNS records have been added to an existing domain.
- Multiple messages of this type may be received for the same domain. This occurs when either the propagation_status or redirection_status changes.
"domain.propagation.timeout": This event is very rare and is triggered if DNS records fail to propagate after 72 hours. It is highly uncommon for domains connected through the automatic flow."domain.flow.completed": Indicates that the user has completed the Entri domain connection flow. This event does not convey any propagation status — it only confirms that the user finished the flow steps.
Status fields
-
propagation_status: The status of DNS record propagation. Possible values:"pending": DNS records are still being propagated."success": DNS records have been successfully propagated."failed": DNS record propagation has failed. This is triggered if the records are not propagated even after 72 hours."exempt": Only present in notifications withtype:"purchase.confirmation.expired".
-
dkim_status: The status of DKIM (DomainKeys Identified Mail) configuration. Possible values:"pending": DKIM setup is pending."success": DKIM configuration has been successfully completed."failed": DKIM setup failed."exempt": DKIM setup is exempt, usually if the user does not use a supported email provider (e.g. Google or Microsoft).
-
redirection_status: The status of domain redirection. Possible values:"pending": Redirection setup is in progress."success": Redirection setup has completed successfully."failed": Redirection setup failed."exempt": Redirection is exempt from this setup.
-
setup_type: Indicates whether the setup was done automatically or manually. Possible values:"automatic": Setup was performed automatically."manual": Setup required manual intervention."async": Setup was done using the DNS asynchronous update."api": The setup was performed using the Entri Sell Enterprise API
Advanced DMARC configuration feature
This field is present in the webhook when using the DMARC Handling: Advanced Options orvalidateDmarc features.
dmarc_updated: Reflects the status of DMARC (Domain-based Message Authentication, Reporting, and Conformance) updates. Possible values:"true": DMARC settings have been updated."false": DMARC settings were not updated."exempt": DMARC is not applicable in this situation (e.g. for domains that don’t require it).
Data object (DNS records)
Thedata object contains the DNS records that have been propagated and those that are pending.
-
records_propagated: An array of DNS records that have been successfully propagated. Each record contains:-
type: The type of DNS record (e.g."A","CNAME"). -
host: The hostname for which the DNS record applies (e.g."smallbusiness.com"). -
value: The value of the DNS record (e.g."54.153.2.220"). -
applicationUrl: (optional, Entri Power only) The application URL tied to the propagated DNS record (e.g."www.example.com"). -
powerRootPathAccess: (optional, Entri Power only) An array of paths accessible through Entri Power. Example:
-
-
records_non_propagated: An array of DNS records that have not yet propagated. The structure is the same asrecords_propagated.
Shared flows
When a flow is initiated via a sharing link or with asharedFlowId, webhook events include an origin_flow_id to correlate the derived flow back to the origin. See Shared Links for details.
Frontend event: onSharedFlowSent
When using shared flows in the frontend experience, Entri exposes anonSharedFlowSent callback that fires when a user copies a shared flow and reaches the shared-flow congratulations screen.
This event includes the sharedFlowId, allowing you to bind:
- the sharedFlowId (originating / shared flow)
- the derived flow run that completes later (via
origin_flow_idin webhooks)
Browser callback events
The following events are useful for following up the user’s navigation and take action under certain circumstances, for example, leading the user to your manual setup guide in case you don’t want to use Entri’s.onSuccess Callback Event
This event is triggered when the user reaches the Congratulations screen in Entri Connect and Entri Sell, regardless of whether the setup was automatic or manual. Use this event to capture a definitive success signal and the jobId that identifies the flow.
Sample usage:
JavaScript
Sample event.detail object response:
JSON
Event details object description
The
onSuccess event complements existing browser events and is the recommended source to capture the jobId for subsequent server-side operations (e.g., retrieving the last webhook or triggering a propagation re-check).onEntriClose Callback Event
This event gets triggered as soon as the modal is closed, giving you back useful information about the latest status of the flow.
Sample usage:
JavaScript
Sample event.detail object response:
JSON
Event details object description
Errors description available at the Possible error codes section.
lastStatus possible values
onEntriManualSetupDocumentationClick Event
This event is triggered when the user has clicked on the “Follow our step-by-step guide” link on the Manual configuration screen. It doesn’t include any additional information within the event.detail object. This is useful for triggering proprietary javavascript based solutions when the user needs help with configuring the manual flow, e.g. opening support chats, etc.
Sample usage:
JavaScript
onEntriStepChange Event
This event is triggered each time a different screen is shown within the Entri configuration process. It serves the purpose of offering additional user journey insights, making it useful for implementing listeners and triggering third-party tracking system events when necessary.
Sample usage:
JavaScript
Sample event.detail object response:
JSON
Event details object description
Errors description available at the Possible error codes section.
step possible values
onEntriRequestClose Event
This event lets host applications run their own confirmation UI (or cleanup logic) when the user clicks the close (X) button, instead of Entri’s built‑in “Are you sure you want to leave?” dialog.
This event is gated by
whiteLabel.customProperties.general.useCustomExitConfirmation. Set it to true to enable the event; otherwise Entri shows its own default exit confirmation dialog and this event does not fire.entri.close() to dismiss the widget. The regular onEntriClose event then fires through the normal close flow.
Sample usage:
JavaScript

