AMS Integration: AMS360 Web Services (SOAP)

The AMS360 Web Services (SOAP) integration connects Broker Buddha AI to Vertafore AMS360 over the SOAP WSAPI so BB AI can read the account executive and account representative codes attached to your insureds — and map them to the right roles in BB AI (Primary POC, Account Manager, Producer, CSR, Marketer).

This is a separate connection from the JSON-based EMS API integration (AMS Integration: Vertafore AMS360 (EMS API)). Many agencies run both side by side: EMS API handles the bulk data sync, and the SOAP WSAPI handles the role/code mapping that the EMS API doesn't expose.

🔐 Who can configure this integration? Only Account Owners and Billing Managers can set up or change integrations. Standard Users do not have access to the Settings → Integrations area.

🤔 SOAP WSAPI vs. EMS (JSON) API — Which Do I Need?

💡 Most agencies enable both: EMS API for the data, and SOAP WSAPI for the role mapping. The two integrations are configured on separate pages and use separate credentials.

✅ Before You Begin

You'll need the following from AMS360:

• Agency number — the same AgencyNo  you use for WSAPI login
• WSAPI Login ID — created inside AMS360 under Admin → Web Services API
• Password — set when creating the WSAPI login
• Service base URL — defaults to https://wsapi.ams360.com/v3  and rarely needs to change

You'll also need access to AMS360's Admin → Web Services API (or someone on your team who does) to create the WSAPI credentials.

💡 These WSAPI credentials are separate from the EMS App Access Key. Even if you've already configured the EMS API integration, you'll need a new set of WSAPI credentials for SOAP.

🧭 Opening the AMS360 Web Services Configuration

Step 1: Go to Settings ⚙️ → Integrations. Step 2: Click the Available sub-tab. Step 3: Find the AMS360 Web Services card under Agency Management Systems. Step 4: Click Configure.

🖼️ [Image placeholder: screenshot of the Integrations Available tab with the AMS360 Web Services card highlighted]

You'll land on the AMS360 Web Services configuration page. Until credentials are saved and the integration is enabled, the status badge at the top reads Inactive.

📘 How the Integration Works

The page header explains the model:

SOAP WSAPI credentials used with Vertafore EMS for account executive and representative codes. While the integration is inactive, role mappings are part of the configuration below and are saved when you enable. When active, you can change mappings in a separate section without updating connection settings. EMS JSON API credentials are configured separately under Vertafore AMS360 EMS.

In plain language:

• While inactive, the connection settings and the role mappings are saved together when you enable.
• Once active, you can change the role mappings on their own without re-entering credentials.

🖼️ [Image placeholder: screenshot of the AMS360 Web Services page header showing the Inactive status badge and the description block]

⚙️ Configuring the Integration

The Configuration section holds the WSAPI credentials and role mapping. There's a "See setup instructions below" link if you need to jump to the AMS360-side steps.

Step 1: Enter Your WSAPI Credentials

• Agency number (required) — the same agency number you use for WSAPI login (AgencyNo )
• WSAPI login ID (required) — the Login ID you created in AMS360's Web Services API admin
• Password (required) — your WSAPI password
• Service base URL — defaults to https://wsapi.ams360.com/v3 . The SOAP endpoint is …/WSAPIService.svc . Leave this as-is unless Vertafore Support tells you otherwise.

🖼️ [Image placeholder: screenshot of the Configuration section with the four credential fields]

Step 2: Configure Insured Role Mapping

The Insured role mapping section lets you decide how BB AI's insured roles are populated from AMS360. Each BB AI role is a dropdown — choose whether it's filled from the Account executive code, the Account representative code, or None (not synced from WSAPI).

The five mappable roles are:

• Primary POC
• Account manager
• Producer
• CSR
• Marketer

💡 These choices are stored when you save credentials by enabling the integration. Once the integration is active, you can adjust them later without updating your WSAPI credentials.

🖼️ [Image placeholder: screenshot of the Insured role mapping section with the five dropdowns and example selections]

Step 3: Test the Connection

Above the footer buttons you'll see this reminder:

"Run Test Connection successfully before you can enable this integration."

Click Test Connection to verify your credentials. A successful test enables the Enable Integration button.

Step 4: Save and Enable

The footer has four buttons:

• Cancel — discards changes and returns to the Integrations list
• Test Connection — verifies credentials without enabling
• Enable Integration — saves the configuration and activates the connection
• Disable Integration — turns off an active integration (only relevant once enabled)

🖼️ [Image placeholder: screenshot of the footer buttons: Cancel / Test Connection / Enable Integration / Disable Integration]

📋 Setup Instructions: Creating WSAPI Credentials in AMS360

The configuration page includes a Setup Instructions card that walks through the AMS360 side. Reproduced here for reference:

Create dedicated WSAPI credentials in AMS360 Admin. These are separate from Vertafore EMS (JSON) credentials configured on the Vertafore AMS360 EMS page.

Steps:

1. In AMS360, go to Admin → Web Services API.
2. Click New.
3. Set Web Service Application to Custom.
4. Create a WSAPI Login ID and password for Broker Buddha / BB AI to use.
5. Set Data security based on "Entity Access Security Only".
6. Under entity access, check all options so the integration can read required customer data.
7. Enter the same agency number, login ID, and password here in BB AI (default service URL is usually correct).

🔗 Helpful link: Vertafore AMS360 support (linked from the Setup Instructions card)

🖼️ [Image placeholder: screenshot of the Setup Instructions card showing the 7-step list]

🔧 Changing Role Mappings After Enabling

Once the integration is Active, role mappings live in their own section that you can update without touching connection settings — meaning you can re-map who fills the Producer or CSR slot without re-entering your WSAPI password.

💡 If your agency reorganizes roles or changes how account executives and account representatives are assigned in AMS360, revisit the role mapping section so BB AI keeps reflecting reality.

💡 Best Practices

• Create dedicated WSAPI credentials for BB AI. Don't reuse a personal AMS360 user's WSAPI login — create a purpose-built one so it's easy to audit and rotate.
• Enable Entity Access Security Only on the WSAPI account, with all entity-access options checked, so BB AI can read the data it needs.
• Always run Test Connection before clicking Enable. The Enable Integration button is intentionally locked behind a successful test.
• Pair with the EMS API integration. The SOAP WSAPI integration provides role/code mapping; the EMS API provides bulk data. Most agencies need both.
• Review your role mappings annually (or whenever your agency restructures) so the mappings stay aligned with how AMS360 is actually used.
• Leave the Service base URL alone unless Vertafore Support asks you to change it.