# Requirements for Vertafore AMS360 integrations

**URL:** <https://community.synatic.com/t/requirements-for-vertafore-ams360-integrations/233>\
**Category:** Connections\
**Tags:** helper-functions, connection\
**Created:** [May 18, 2022, 9:04am UTC](https://community.synatic.com/t/requirements-for-vertafore-ams360-integrations/233 "2022-05-18T09:04:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![navessa](https://yyz2.discourse-cdn.com/flex032/user_avatar/community.synatic.com/navessa/32/58_2.png) [@navessa](https://community.synatic.com/u/navessa)\
**Post date:** [May 18, 2022, 9:04am UTC](https://community.synatic.com/t/requirements-for-vertafore-ams360-integrations/233/1 "2022-05-18T09:04:58Z")

</div>

The following are the **requirements** that are needed in order to have a successful **Vertafore AMS360 integration** :

**1. Sandbox:**

A **sandbox is required** for testing purposes in the development organization. If there is no sandbox to test on, the implementation cannot be done.

**2. WSAPI:**

a. Fetch core items such as customers, contacts and policy headers.  
b. Write back customers, vendors, contacts and policy headers (schedule details download through IVANs).

**3. VPN:**

a. Fetch additional information from the database.  
b. SQL connection via VPN.  
c. Policy schedules, detailed comm deals – not sure of the full list but need to come up with several examples of what VPN requires.  
d. How Synatic’s relay works in tandem with this.  
e. No write back capability.

**Additional information:**

The below link consists of **Vertafore’s API references** :

> [API Documentation](https://link.vertafore.com/VERTAFORE/overview)