Vertafore AMS360
Vertafore AMS360 is a cloud agency management system for independent insurance agencies, covering policy management, customer records, accounting, and document management. It is one of the most widely used AMS platforms for personal and commercial lines agencies in North America.
What you can do
Read and write client and policy records
Pull client master data with contact details, account type, and linked policies. Read policy details including carrier, coverage line, premium, and expiration date. Write back updated client information from your CRM or onboarding product.
Sync activity and communication history
Read activities, notes, and suspense items by client or policy. Create new activities from your customer-success or renewal product to maintain a complete interaction history in AMS360.
Access claims and loss records
Pull claims associated with a policy including loss date, claimant, status, and reserve. Useful for claims-analytics or reporting products that need to correlate claim frequency with account and policy data.
Read certificates of insurance
Pull issued certificate records by client or policy including holder details, coverage effective dates, and expiry. Askel surfaces certificate data for products that automate certificate issuance or renewal tracking.
Sync producer and commission data
Read producer assignments, split commission percentages, and commission statements from AMS360's accounting module. Useful for compensation-management products that need to validate commission calculations.
Access accounting transactions
Pull invoices, payments, and direct-bill statements from the AMS360 accounting module. Useful for financial-reporting products that need to consolidate agency revenue data with other sources.
Pulling AMS360 policy data into a commercial lines quote-comparison tool
BlueStar Independent Insurance manages 3,500 small-business clients in AMS360. They have deployed your commercial lines quote-comparison platform to help their producers run multi-carrier quotes faster. When a producer opens a client in the platform, they need to see the client's current policies and coverage details from AMS360 automatically rather than re-entering them.
- 1
Register the OAuth client via the Vertafore developer portal
BlueStar's IT administrator navigates to the Vertafore developer portal, creates an OAuth application for Askel, and notes the client ID and client secret. They then link this OAuth application to BlueStar's AMS360 organization in the AMS360 API settings.
- 2
Enter credentials in Askel
BlueStar's admin enters the AMS360 API endpoint URL, client ID, and client secret into the Askel setup screen inside your quoting platform. Askel exchanges the credentials for an access token via Vertafore's OAuth endpoint and confirms connectivity by fetching the client list.
- 3
Schema discovery
Askel reads the AMS360 API objects the OAuth client can access and identifies the Client, Policy, Line of Coverage, and Activity objects along with any custom fields BlueStar has configured. Your CS team sees a mapping draft within minutes.
- 4
Map and validate
BlueStar uses an AMS360 user-defined field to track a client's preferred carrier tier. A CS rep maps this to the quoting platform's carrier-preference filter and runs a dry-run against 200 client records to confirm policy details and coverage data load correctly.
- 5
Go live
Producers open a client in the quoting platform and see their current AMS360 policies and coverage details pre-populated. Quote submissions automatically carry the client ID so completed quotes link back to the correct AMS360 client record.
Service account
The customer's agency administrator registers an OAuth client in the Vertafore developer portal, links it to their AMS360 organization, and provides the client ID and client secret to Askel. Askel exchanges these for an access token via Vertafore's OAuth identity provider and refreshes it automatically before expiry.
How Askel sits between your product and the customer's system
FAQ for Vertafore AMS360
Does every AMS360 customer have access to the Vertafore API?+
Is the Vertafore developer portal separate from the AMS360 application?+
What OAuth scopes does the AMS360 client need?+
How are AMS360 custom (user-defined) fields handled?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.