AgentVizion
AgentVizion is Magnifact's patented, SOC 2 Type II-compliant insurance distribution intelligence platform. It provides national agencies, insurance carriers, and their downline agents with a secure, cloud-based, 360-degree view of their book of business across multiple carriers, product lines (Health, Life, and Annuities), and distribution channels. AgentVizion automates data aggregation across pre-sales, post-sales, commissions, payments, applications, and production data—eliminating manual downloads and spreadsheets—while offering real-time RESTful APIs that connect carriers with distributors in alignment with IRI Digital First for Annuities standards.
Power end-to-end data operations for your AgentVizion API with Nexla. Our bi-directional AgentVizion connector is purpose-built for AgentVizion, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to AgentVizion or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your AgentVizion workflows fast, secure, and fully governed.
Features
Type: API
- Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
- Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
- API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
- Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Prerequisites
AgentVizion is Magnifact's SOC 2 Type II-compliant insurance distribution platform. Access to the AgentVizion API is provisioned by Magnifact and requires an active AgentVizion subscription. API credentials are not self-service—they are issued by Magnifact's implementation or support team as part of your onboarding or API enablement engagement.
Before creating a credential in Nexla, work with Magnifact to obtain the API credentials required for authentication:
-
Contact your Magnifact account representative or the Magnifact support team to request API access for your AgentVizion account. If you do not yet have an AgentVizion account, visit magnifact.com to learn more about the platform and request a demo or subscription.
-
Magnifact will provision API access for your organization and supply the following credentials:
- API Key — A unique key that authenticates your organization's API requests to the AgentVizion platform.
- Base URL — The base URL for your AgentVizion API instance (e.g.,
https://api.agentvizion.com). This may be specific to your organization or deployment.
-
Store your API key securely. The API key grants access to your organization's insurance distribution data, including agent book-of-business, production, commissions, and carrier application data. Treat it with the same care as a password.
Do not share your AgentVizion API key with unauthorized parties. If you believe your API key has been compromised, contact Magnifact support immediately to have it rotated.
- For questions about API enablement, available endpoints, and integration scope, refer to the AgentVizion API Services page or contact Magnifact directly.
Authenticate
Credentials required
Fetches a session token using an API Key, then uses the token.
| Field | Required | Secret | Description |
|---|---|---|---|
| AgentVizion Base URL | Yes | No | The AgentVizion base URL. The part of the URL that comes before agentvizion.com. If the API URL is https://sample-api.agentvizion.com/api, then set this value to sample-api |
| API Key | Yes | Yes | Your AgentVizion API key |
Create a credential in Nexla
AgentVizion uses API key-based authentication. The API key is passed as a request header on all calls to the AgentVizion REST API, identifying your organization and authorizing access to your data.
-
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
-
Enter the AgentVizion API key issued by Magnifact in the API Key field. This key authenticates Nexla's requests to the AgentVizion platform on behalf of your organization.
-
Enter the base URL for your AgentVizion API instance in the Base URL field. This is the root URL provided by Magnifact for your organization's deployment (e.g.,
https://api.agentvizion.com). All API endpoint paths are appended to this base URL.The Base URL is specific to your AgentVizion deployment. Confirm this value with your Magnifact account representative if you are unsure which URL applies to your account.
-
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Use as a data source
The AgentVizion connector enables you to ingest insurance distribution data from Magnifact's AgentVizion platform into Nexla data flows. This connector is particularly useful for applications that need to consolidate agent book-of-business data, production metrics, commissions, pending application statuses, and carrier-integrated data from across your distribution network for reporting, analytics, and downstream processing.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the AgentVizion connector tile, then select the credential that will be used to connect to the AgentVizion instance, and click Next; or, create a new AgentVizion credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common AgentVizion endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Manual configuration
AgentVizion data sources can also be manually configured to ingest data from any valid AgentVizion API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
AgentVizion exposes RESTful API endpoints for key insurance distribution data objects. Common endpoint patterns include:
- Agent and agency production data (e.g.,
/api/v1/agents,/api/v1/production) - Pending and submitted application statuses (aligned with IRI Digital First for Annuities Activity Status API standards)
- Commission and payment data (e.g.,
/api/v1/commissions) - Book-of-business records across carriers and product lines (Health, Life, Annuities)
- Carrier-integrated data feeds via DTCC connectivity
Contact your Magnifact account representative or refer to the AgentVizion API Services documentation for the full list of available endpoints and their URL structures. The AgentVizion API key authentication header is handled automatically by Nexla based on your credential configuration and does not need to be added as a request header.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new AgentVizion data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Use as a destination
Click the + icon on the Nexset that will be sent to the AgentVizion destination, and select the Send to Destination option from the menu. Select the AgentVizion connector from the list of available destination connectors, then select the credential that will be used to connect to the AgentVizion organization, and click Next; or, create a new AgentVizion credential for use in this flow.
Manual configuration
AgentVizion destinations can be manually configured to send data to any valid AgentVizion API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
For most write operations in AgentVizion, the appropriate method is POST (to submit new records) or PUT/PATCH (to update existing records), and AgentVizion's REST API accepts data in JSON format for most write operations. For update/upsert operations, include the ID of the object to be updated at the end of the URL.
AgentVizion API endpoints accept data submissions for various insurance distribution objects. Common write endpoint patterns include:
- Submitting or updating agent records
- Posting production or sales data
- Updating application or case status records
- Sending commission or payment data
Consult the AgentVizion API Services documentation or your Magnifact account representative for the complete list of available write endpoints and their expected request formats. The AgentVizion API key authentication header is handled automatically by Nexla based on your credential configuration and does not need to be added as a request header.
Save & activate
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured AgentVizion endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the AgentVizion API until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.