Skip to main content

​
Event Types

Midbound sends webhook events at different stages of the visitor identification and enrichment process. Subscribe to the events that match your use case.
EventBest For
identity.resolvedImmediate on-site personalization
identity.qualifiedSales alerts and lead routing
identity.enrichedLead scoring, CRM sync, marketing automation
identity.validatedEmail list hygiene, deliverability optimization
identity.session.finalizedAttribution modeling and historical reporting
Start with identity.enriched - it includes the most comprehensive data for most use cases.

Data Dictionary

Interactive field-by-field payload reference with type badges, nullability, and full example values for every event.

SDKs

Typed webhook payloads and verification helpers available for TypeScript, Python, and Go.

​
Event Pipeline

Events flow through a processing pipeline where each stage builds on the previous: 
identity.resolved → identity.qualified → identity.enriched → identity.validated
                                                           ↘ identity.session.finalized
Subscribing to a later-stage event (e.g., identity.validated) means all prerequisite processing will run automatically.

​
identity.resolved

Fired the moment a visitor is recognized by the system. Optimized for maximum speed, provides the core unique identifier and basic session metadata. Best used for immediate on-site personalization where millisecond-level latency is critical. See the API Reference for the full payload schema and examples, or the Data Dictionary for an interactive field-by-field breakdown.

​
identity.qualified

Fired once the identity is verified with professional-grade data points. Guarantees delivery of essential attributes such as LinkedIn profiles, current job titles, and primary company information. Same payload structure as identity.resolved with professional fields guaranteed non-null. See the API Reference for the full payload schema and examples, or the Data Dictionary for an interactive field-by-field breakdown.

​
identity.enriched

Fired once the full intelligence gathering process is complete. Delivers the most comprehensive payload available, including person profile (LinkedIn, employment, skills), company data (funding, headcount, SEO, web traffic), and email validations. See the API Reference for the full payload schema and examples, or the Data Dictionary for an interactive field-by-field breakdown.
The full payload includes 50+ fields across person profile, company data, and email validations.

​
identity.validated

Fired when email validation completes. Contains validation results per email including deliverability status and provider information. See the API Reference for the full payload schema and examples, or the Data Dictionary for an interactive field-by-field breakdown. Validation statuses:
  • valid — Email is deliverable
  • invalid — Email does not exist or is undeliverable
  • catch_all — Domain accepts all emails (cannot verify specific address)
  • valid_catch_all — Domain is catch-all but the specific address appears valid

​
identity.session.finalized

Fired after a session has concluded due to inactivity. Includes full session events (page-level activity), enrichment data (person + companies), and finalization metadata. See the API Reference for the full payload schema and examples, or the Data Dictionary for an interactive field-by-field breakdown.
The data.enrichment block is identical to identity.enriched. The data.session block extends the shared session structure with events[], lastActivity, and enrichments[].