.png)
Vertafore Integration Guide
Vertafore integrates with enterprise systems through product-specific APIs, partner programs, event mechanisms, and document workflows that vary by application and authorization.
Vertafore integration options at a glance
Vertafore provides product-specific API and technology-partner integration capabilities across applications such as AMS360, Sagitta, BenefitPoint, ImageRight, and PL Rating. REST-oriented access may be available, but endpoints, objects, authentication, and authorization vary by product, subscription, deployment model, and partner approval. Selected products may also provide event notifications, callbacks, file exchange, document workflows, or import and export functions. Martini can consume documented Vertafore APIs, receive supported webhook-style requests, orchestrate workflows, transform insurance data, and expose controlled APIs to downstream applications. Direct database access and a universal Vertafore-wide GraphQL, SOAP, or bulk API should not be assumed.
| Integration point | Supported by Vertafore? | Common use cases | How Martini supports it |
|---|---|---|---|
| Product-specific REST APIs | Limited | Use documented APIs to retrieve or update Customers, Accounts, Policies, Contacts, Activities, Claims, or product-specific benefits and document data. Availability depends on the Vertafore product, edition, subscription, and authorization. | Martini can consume documented Vertafore REST endpoints, transform responses, apply business rules, and write to target applications or expose a controlled internal API. |
| Webhooks and outbound callbacks | Limited | Selected Vertafore products or partner programs may provide event notifications or outbound callbacks for supported changes. Universal coverage of customer, policy, claim, activity, or document changes is not confirmed. | Martini can receive supported webhook-style requests, validate and correlate them, retrieve current Vertafore data when needed, and start downstream workflows. |
| File and document integration | Limited | ImageRight and related insurance workflows may involve documents, folders, files, and metadata. Attachment APIs, formats, limits, and transfer methods vary by product and deployment. | Martini can orchestrate supported file or metadata transfers, map document attributes, apply classification rules, and record processing status. |
| Authentication and authorization | Limited | Access is product- and partner-specific and may require customer consent, application credentials, scopes, roles, tenant identifiers, or partner approval. No universal Vertafore authentication standard was confirmed. | Martini can keep credentials in environment configuration or secrets management and use the authentication flow documented for the selected Vertafore API. |
| Import, export, and batch processing | Not confirmed | Product-specific imports, exports, or scheduled processing may exist, but a common Vertafore-wide bulk or asynchronous API was not confirmed. | Martini can orchestrate documented exports or imports when available, including validation, transformation, checkpointing, and exception handling. |
| SOAP or XML services | Not confirmed | Historical or product-specific SOAP or XML services may exist, but a current Vertafore-wide SOAP recommendation was not verified. | Martini can consume a confirmed Vertafore SOAP service if the selected product documents one, while keeping the implementation isolated and version-aware. |
| SDKs and partner tooling | Limited | Vertafore supports technology-partner and integration programs, but a single universal public SDK was not confirmed. | Martini can use documented HTTP interfaces or approved client tooling where required, while centralizing orchestration and transformations in workflows. |
| Direct database access | No | Direct access to hosted Vertafore databases should not be assumed. Supported APIs, exports, or integration services should be used instead. | Martini can connect to approved external databases for staging or reporting, but should not query Vertafore internal databases without explicit vendor documentation and approval. |
How Vertafore exposes data and business events
Vertafore REST APIs
Vertafore provides product-specific API and technology-partner capabilities, including REST-oriented integrations where documented. Resources, operations, authentication, pagination, and authorization vary across AMS360, Sagitta, BenefitPoint, ImageRight, PL Rating, and other products.
Martini implementation pattern
Martini implementation pattern: Martini authenticates against the selected product endpoint, retrieves or updates documented resources, maps product-specific payloads into canonical models, applies insurance business rules, and sends results to downstream systems or exposes them through a Martini API.
Implementation sequence
Vertafore Webhooks and Callbacks
A universal Vertafore webhook framework was not confirmed. Selected products or partner programs may support event notifications or outbound callbacks for particular event types, so coverage must be verified before design.
Martini implementation pattern
Martini implementation pattern: Martini exposes a secured receiving endpoint or workflow trigger for the confirmed callback, validates the request, correlates the event to a Vertafore object, and retrieves the current resource when the notification does not contain a complete payload.
Implementation sequence
Vertafore File and Document Workflows
ImageRight and related insurance processes make document, folder, file, and metadata exchange relevant. Supported attachment operations, formats, limits, and retention behavior vary by product and deployment.
Martini implementation pattern
Martini implementation pattern: Martini coordinates approved document or metadata operations, applies naming and classification rules, transfers supported content, and stores source-target correlation and processing status without exposing sensitive values in logs.
Implementation sequence
Vertafore Imports and Exports
Product-specific imports, exports, batch functions, or scheduled processing may be available, but a common Vertafore-wide bulk API was not confirmed. Each operation must be validated against the selected product.
Martini implementation pattern
Martini implementation pattern: Martini schedules or orchestrates an approved export or import, validates file or payload structure, transforms records into the target schema, checkpoints progress, and produces reconciliation results for rejected rows.
Implementation sequence
Common Vertafore integration patterns
Pattern 1: Synchronize agency customers and contacts
When to use this pattern
Use this pattern when Salesforce or Microsoft Dynamics 365 must share customer and contact information with AMS360 or Sagitta. Define field ownership and matching rules before enabling bidirectional updates to prevent duplicate customers and conflicting contact details.
Integration direction
Example Mapping
| Vertafore Field | Canonical Field | Target Field |
|---|---|---|
| Customer.id | sourceCustomerId | External_Customer_ID__c |
| Customer.name | customerName | Account.Name |
| Contact.email | contactEmail | Contact.Email |
| Contact.phone | contactPhone | Contact.Phone |
Martini implementation pattern
A Martini workflow retrieves changed Vertafore Customers and Contacts through the authorized product API, or processes an approved callback. It validates required fields, resolves matches using stable identifiers, applies source-of-truth rules, updates the CRM, and sends validation, duplicate, or authorization failures to an exception path. Retries are limited to transient failures.
Martini capabilities used
- workflows
- API consumption
- data mapping
- business rules
- error handling
Pattern 2: Distribute policy and account data
When to use this pattern
Use this pattern when downstream systems such as ServiceNow, Power BI, or a reporting platform need selected Vertafore Accounts and Policies without direct database access. It is appropriate for scheduled or event-assisted synchronization of renewals, endorsements, cancellations, and other policy changes.
Integration direction
Example Mapping
| Vertafore Field | Canonical Field | Target Field |
|---|---|---|
| Account.id | sourceAccountId | Account.ExternalId |
| Policy.policyNumber | policyNumber | PolicyNumber |
| Policy.effectiveDate | effectiveDate | EffectiveDate |
| Policy.status | policyStatus | Status |
Martini implementation pattern
Martini schedules incremental API retrieval where the product supports timestamps or change tokens, preserves policy-term and transaction identifiers, filters sensitive fields, and maps the result to the target model. The workflow checkpoints progress, handles pagination and throttling, and reconciles failed or missing objects rather than silently dropping them.
Martini capabilities used
- scheduled workflows
- API consumption
- data mapping
- business rules
- monitoring
Pattern 3: Coordinate ImageRight document workflows
When to use this pattern
Use this pattern when ImageRight or another Vertafore document surface must exchange approved files or metadata with SharePoint, Salesforce, ServiceNow, or DocuSign. Confirm binary operations, file limits, retention, and authorization before implementation.
Integration direction
Example Mapping
| Vertafore Field | Canonical Field | Target Field |
|---|---|---|
| Document.documentId | sourceDocumentId | ExternalDocumentId |
| Document.fileName | documentName | Name |
| Document.documentType | documentType | ContentType |
| Document.createdDate | createdAt | CreatedDate |
Martini implementation pattern
A Martini workflow retrieves supported ImageRight metadata or content references, applies document classification and naming rules, transfers permitted content or metadata, and stores a correlation record. Idempotency keys prevent duplicate files, while size, malware, authorization, and transfer errors are routed to operational review.
Martini capabilities used
- workflows
- file processing
- data mapping
- business rules
- error handling
Pattern 4: Synchronize BenefitPoint benefits data
When to use this pattern
Use this pattern when BenefitPoint data such as groups, plans, enrollments, or carriers must be reconciled with Workday, a CRM, payroll, or analytics platform. Product-specific object names and partial-update behavior must be confirmed first.
Integration direction
Example Mapping
| Vertafore Field | Canonical Field | Target Field |
|---|---|---|
| Group.groupId | benefitGroupId | OrganizationId |
| Plan.planId | planId | BenefitPlanId |
| Enrollment.effectiveDate | enrollmentEffectiveDate | EffectiveDate |
| Carrier.name | carrierName | ProviderName |
Martini implementation pattern
Martini retrieves or receives approved BenefitPoint data, validates effective dates and identifiers, maps the product-specific model, and reconciles accepted and rejected changes. Sensitive benefits data is minimized in payloads and logs, and transient failures are retried while validation and authorization failures are reported.
Martini capabilities used
- workflows
- API consumption
- data mapping
- validation
- error handling
Applications commonly integrated with Vertafore
Vertafore products often participate in broader insurance, agency-management, benefits, document, and reporting architectures. The exact integration surface must be confirmed for the selected Vertafore product and customer authorization; the relationships below describe practical enterprise integration scenarios rather than guaranteed packaged integrations.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize agency customers, contacts, opportunities, activities, and selected policy information. | Vertafore → Martini → Salesforce | Martini retrieves or receives authorized Vertafore data, applies customer-matching and field-ownership rules, transforms insurance objects into Salesforce payloads, and routes validation or duplicate exceptions for review. |
| Microsoft Dynamics 365 | Connect CRM account and contact management with agency-management customer and policy data. | Vertafore → Martini → Microsoft Dynamics 365 | A Martini workflow coordinates incremental Vertafore retrieval and Dynamics 365 updates, preserves source identifiers, applies bidirectional conflict rules, and retries only transient failures. |
| ServiceNow | Make customer, policy, claim, or service activity information available to service-management workflows. | Vertafore → Martini → ServiceNow | Martini normalizes selected Vertafore objects, filters sensitive fields, and calls ServiceNow APIs or exposes an internal API for controlled case and service-process updates. |
| SharePoint | Organize insurance documents and metadata alongside ImageRight or agency records. | Vertafore → Martini → SharePoint | Martini transfers supported document metadata or files, applies naming and classification rules, records source and target identifiers, and handles size, duplicate, and authorization exceptions. |
| Workday | Exchange employee, benefits, or organizational information where BenefitPoint participates in benefits processes. | Workday → Martini → Vertafore | Martini validates effective dates and identifiers, maps Workday data to the selected BenefitPoint model, reconciles partial changes, and produces an exception report for rejected records. |
| NetSuite | Align agency billing, finance, or customer information with Vertafore agency-management data. | Vertafore → Martini → NetSuite | A scheduled Martini workflow retrieves authorized account or policy data, applies finance-specific mappings and business rules, and writes idempotent NetSuite updates with operational reconciliation. |
| Power BI | Load policy, customer, activity, or operational data into reporting models without querying internal Vertafore databases. | Vertafore → Martini → Power BI | Martini retrieves supported API or export data, normalizes product-specific objects into reporting structures, removes unnecessary sensitive fields, and publishes the result through an approved data-loading path. |
| DocuSign | Coordinate document execution or signature status with insurance documents and customer records. | Vertafore → Martini → DocuSign | Martini coordinates document metadata and signature status between authorized Vertafore or ImageRight surfaces and DocuSign, applying correlation IDs, duplicate prevention, and retry handling. |
How to build a Vertafore integration in Martini
Objective
Confirm the exact Vertafore product, deployment model, API package, endpoint, authorization process, and target environment before implementation.
Instructions in Martini
- Identify AMS360, Sagitta, BenefitPoint, ImageRight, PL Rating, or another product
- Confirm partner approval, customer consent, scopes, roles, tenant identifiers, and environment URLs
- Store credentials and secrets in Martini environment configuration
Objective
Select an event-driven, scheduled, API-led, or approved import/export trigger based on the product-specific integration surface.
Instructions in Martini
- Use a confirmed callback or webhook-style request when available
- Use a scheduler for incremental retrieval or approved batch processing
- Define checkpoint and replay behavior before production use
Objective
Receive or retrieve the current Vertafore object and account for pagination, incremental filters, and product-specific response structures.
Instructions in Martini
- Call documented Vertafore endpoints through a Martini workflow
- Handle pagination and updated-since or change-token mechanisms when supported
- Retrieve the current resource after a lightweight event notification when necessary
Objective
Coordinate the end-to-end workflow across Vertafore, Martini, and the destination system with explicit control points.
Instructions in Martini
- Separate retrieval, validation, mapping, business rules, and delivery stages
- Preserve source identifiers and correlation IDs
- Use reusable workflow logic for common authentication and error paths
Objective
Transform product-specific Vertafore objects into a canonical or target application model without assuming schemas are shared across products.
Instructions in Martini
- Map Customers, Accounts, Policies, Contacts, Activities, Claims, or product-specific objects explicitly
- Normalize dates, statuses, identifiers, and policy-term information
- Minimize sensitive insurance and benefits data in payloads and logs
Objective
Enforce matching, idempotency, privacy, ownership, and policy-version rules before writing data.
Instructions in Martini
- Use stable Vertafore identifiers for duplicate prevention
- Validate required fields and effective dates
- Route conflicts, unsupported operations, and validation failures to exceptions
Common Vertafore data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Customer | Represents an agency customer or insured party and supports customer synchronization and matching. | Salesforce, Microsoft Dynamics 365, NetSuite, data platforms | Martini maps product-specific customer fields, preserves the Vertafore identifier, validates required insurance attributes, and applies duplicate-prevention rules. |
| Account | Groups agency or customer-level insurance business and related policies. | Salesforce, ServiceNow, NetSuite, reporting platforms | Martini normalizes account relationships, applies field-ownership rules, and synchronizes changes using documented identifiers and incremental criteria where available. |
| Policy | Represents a policy, policy term, or policy transaction, including renewals, endorsements, cancellations, and reinstatements where exposed. | Salesforce, ServiceNow, data warehouses, Power BI | Martini preserves policy-term identifiers, effective dates, transaction dates, and source versions while filtering sensitive fields and handling pagination. |
| Contact | Represents people or organizations associated with customers, accounts, policies, or agencies. | Salesforce, Microsoft Dynamics 365, ServiceNow, SharePoint | Martini matches contacts using stable source identifiers and controlled fallback rules, then maps relationships and consent-sensitive fields. |
| Activity | Represents tasks, notes, communications, service activities, or workflow-related events. | Salesforce, ServiceNow, reporting platforms | Martini transforms activity types and timestamps, correlates source references, and routes unsupported or invalid activity values to exceptions. |
| Claim | Contains claim-related information where exposed by the selected Vertafore product or integration surface. | ServiceNow, Salesforce, reporting platforms | Martini transfers only authorized claim fields, applies privacy and access rules, and treats missing, closed, or conflicting claims as explicit business outcomes. |
Authentication and security considerations
Product-specific authorization
Vertafore authentication is not uniform across the product portfolio. Confirm the product, environment, credential type, scopes, roles, tenant identifiers, token behavior, and any customer or partner approval before implementation.
Protect insurance data
- Store Vertafore credentials in Martini environment configuration or secrets management.
- Minimize personally identifiable and benefits data in requests, responses, and logs.
- Restrict access to workflows and APIs according to application and agency permissions.
- Confirm whether certificates, client credentials, API keys, or another product-specific method is required.
Operational considerations for Vertafore integrations
Reliability and synchronization
- Confirm pagination, page limits, rate limits, concurrency limits, and incremental retrieval options.
- Use stable Vertafore identifiers, policy-term information, and deterministic idempotency rules.
- Retry transient network and throttling failures with bounded backoff; do not repeatedly retry validation or authorization failures.
- Preserve checkpoints and correlation IDs for replay and reconciliation.
Schema and document controls
- Test product-specific schema changes in a non-production environment.
- Validate effective dates, policy statuses, and partial-update behavior.
- For ImageRight and other document workflows, confirm file formats, size limits, binary transfer, retention, and duplicate handling.
- Monitor non-success responses and route unsupported product operations to an operational exception process.
Why use Martini instead of scripts or point-to-point integrations?
One orchestration layer
Vertafore capabilities vary across AMS360, Sagitta, BenefitPoint, ImageRight, PL Rating, and other products. Martini provides a consistent workflow layer for consuming authorized APIs, receiving supported callbacks, transforming product-specific models, and delivering data to enterprise applications.
Maintainable integration logic
- Centralize authentication, mappings, validation, business rules, retries, and exception handling.
- Reuse workflows and controlled APIs across CRM, service, document, benefits, finance, and reporting use cases.
- Keep source identifiers, checkpoints, and reconciliation data for operational support.
- Deploy changes with explicit configuration rather than maintaining disconnected point-to-point scripts.
Frequently asked questions
Vertafore is integrated through product-specific APIs and technology-partner programs, with REST-oriented access where documented. Selected products or partner programs may also provide callbacks, event notifications, document workflows, or imports and exports. Availability depends on the product, deployment model, subscription, authorization, and partner approval.
Yes. Martini can integrate with Vertafore by consuming the selected product's documented APIs, receiving supported webhook-style requests or callbacks, orchestrating approved file or document exchanges, mapping insurance data, and exposing controlled APIs to downstream applications. The specific Vertafore product and API must be verified first.
No. A dedicated Vertafore connector is not required. Martini can use Vertafore's confirmed product-specific APIs, callbacks, file mechanisms, authentication methods, and other approved integration endpoints through workflows and APIs.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Vertafore. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Vertafore, cloud infrastructure, or other third-party systems depending on subscription, usage, and deployment model.
Use the selected product's documented REST API or approved partner integration first. Treat callbacks, event notifications, file exchange, imports, exports, and SOAP or XML services as product-specific options that require confirmation. Do not assume a universal GraphQL, bulk, database, or SOAP capability.
A universal Vertafore webhook framework was not confirmed. Selected products or partner programs may support callbacks or event notifications for particular event types, but complete coverage of customer, policy, claim, activity, and document changes should not be assumed.
Use an approved incremental-change mechanism where available, supported by stable source identifiers, timestamps, policy-term identifiers, effective dates, and reconciliation logic. Martini can schedule retrieval, process callbacks, map changes, prevent duplicates, and retry transient failures.
Yes. Martini can expose a controlled API that normalizes selected Vertafore Customers, Accounts, Policies, Contacts, Activities, Claims, or document metadata for downstream applications. The façade can centralize authorization, field filtering, transformation, business rules, and error handling.
Related Martini documentation
Plan your Vertafore integration
Confirm the Vertafore product, API package, authorization model, and synchronization requirements, then use Martini to build a maintainable workflow for orchestration, transformation, security, and operational handling.