AMS360 connector evaluation
Decla for AMS360
Evaluate AMS360 automation at the operation level: which interface it uses, what your agency permits, and how the result is checked. Decla is an AI workforce for insurance agencies, built around connected tools and agency processes.
Talk through your agency's workflows
See Decla with your team
Book a demo to walk through how Decla fits the day-to-day work your agency team handles, and where to start.
Discuss your AMS360 workflowOn this page
- Start with the task you need to run
- Confirm the interface and agency permissions
- Separate provider operations from Decla verification
- Test one retrieval task before expanding scope
- Define what acceptance requires
- Review writes and notifications separately
- Bring one AMS360 task to the conversation
- Frequently asked questions
Start with the task you need to run
For an agency systems or operations owner, the useful question is whether a specific customer, policy or activity task can run with the right access and review. Use the distinctions below to scope a demonstration; provider API documentation alone does not establish an enabled Decla operation.
Confirm the interface and agency permissions
Vertafore lists Web Service API (WSAPI) 2.4 and 3.0, OData and Enterprise Management Service (EMS) as AMS360 APIs, and identifies EMS as its preferred, newest API. Ask which interface each proposed task uses; access to one is not evidence of access to another.
WSAPI setup creates an API login and assigns entity actions. Available retrieve, add, update and delete permissions vary by entity. The selected security basis also matters: employee-based options apply business-unit restrictions and exclude secured customers; Entity Access Security Only does not enforce business-unit security and allows secured customers.
Confirm the arrangement with your AMS360 administrator and Vertafore. Its setup guidance distinguishes developing with the separately licensed software development kit (SDK) from using an existing SDK-based program. Do not assume every agency must buy a developer SDK to use an integration.
Sources
- Vertafore API and ONS overview — accessed
- Vertafore WSAPI setup — accessed
Separate provider operations from Decla verification
An HTTP verb is not an operation classification: the commercial-location POST listed below searches records. A payee search cannot create a payee. Evaluate writes separately, including field behavior, permission checks and persisted results.
| Interface / operation | Access to confirm | Read or write? | Provider evidence | Decla scope |
|---|---|---|---|---|
| WSAPI: entity operations | API login, entity action and security basis | Depends on entity/action | Setup guide; exact method docs require access | Unverified here; request exact method proof |
| EMS: POST /policy/commercial-locations/search | EMS access for the proposed policy context | Retrieval | June 26, 2026 notes: PolicyId + TransactionEffectiveDate; paginated results | Unverified here |
| EMS: POST /company/payees/search | EMS access for the proposed company context | Read-only | June 26, 2026 notes: CompanyId; no payee creation or modification | Unverified here |
| EMS: PUT /policy/transaction-premiums | EMS access and applicable policy rules | Update | September 16, 2026 notes: billed premiums restrict some fields; omitted values stay unchanged | Unverified here; separate write acceptance required |
Sources
- Vertafore EMS / API release notes — accessed
Test one retrieval task before expanding scope
Illustrative acceptance plan using synthetic data, not a product result. Suppose your team needs the location list for fictional policy DEMO-POLICY-A at transaction date 2026-07-01 before comparing a property schedule. This tests retrieval scope; it does not test a location update or policy endorsement.
Pin the policy context
Agency systems owner
Agree on the EMS operation, synthetic policy reference and transaction-effective date. Use an authorized test fixture with two expected location identifiers, LOC-A and LOC-B, at the selected transaction date.
Check retrieval completeness
Implementer and agency reviewer
Ask the implementer to show the exact request and every result page, then compare the returned location identifiers and date context with the authorized fixture.
Exercise exceptions
Agency reviewer
Repeat with missing date, wrong policy context and denied access. Require a visible incomplete or access-failure result; an empty response must not be presented as a verified complete schedule.
Decide the scope
Agency operations owner
Record which interface and operation passed, the environment and date, and remaining limits. Keep proposed writes outside the accepted retrieval scope.
Define what acceptance requires
| Check | Acceptance criterion | Evidence status |
|---|---|---|
| Complete retrieval | Both fixture rows returned across all pages; policy/date match | Demonstration required; no test run reported |
| Wrong or missing context | Mismatch or missing date surfaced before treating output as complete | Demonstration required; no test run reported |
| Denied permission | Access failure is distinguishable from no matching records | Demonstration required; no test run reported |
| Proposed write | Show configured approval and persisted readback in a separate authorized test | Outside this retrieval example |
Review writes and notifications separately
For a write demonstration, ask to see the proposed fields before execution, the configured approval rule, and an independent AMS360 readback afterward. Include a denied-permission or invalid-input case. A successful request response is not enough to establish that every intended field persisted.
Outbound Notification Service (ONS) reports changes and may trigger a follow-up API read. Treat notification delivery and successful task completion as separate checks; a notification is not a completed servicing action.
Sources
- Vertafore ONS overview — accessed
Bring one AMS360 task to the conversation
Bring the interface you use, the task you want to run, and the person who owns its permissions and review.
Frequently asked questions
How do I automate COI requests and servicing in AMS360?
Evaluate AMS360 automation at the operation level: which interface it uses, what your agency permits, and how the result is checked. AMS360’s APIs don’t expose master certificate updates, so in that case Decla prepares the work and a person finishes it in the AMS.
What is Decla?
Decla is AI software for independent insurance agencies and brokerages. It connects to your AMS, email and carrier portals and does back-office work inside them. Your team reviews the work before it goes out.