Connect Vertafore AMS360
A step-by-step guide with pictures, from the Speakvora agent's own Connect tab.
Short answer: This connects your own Vertafore account to your Speakvora agent. Then a customer can text where is order 1234 and get the answer in seconds, and the agent can send status and tracking texts. The agent only reads. It can never create, change or delete anything in Vertafore. Only the status word and the order number.
Every key, number and name in the pictures is a made-up example. Nothing here asks you to share a real key with anyone but the app on your own computer.
This connects your own Vertafore account to your Speakvora agent. Then a customer can text *where is order 1234* and get the answer in seconds, and the agent can send status and tracking texts. The agent only reads. It can never create, change or delete anything in Vertafore. Only the status word and the order number are ever texted back, never names, prices, items or addresses.
TIP: You need about 15 minutes, a computer, and the sign-in for your Vertafore account (the owner or a manager). You can't break anything: if a step does not work, nothing has changed and you can just try again. The keys and screens below are made-up examples.
NOTE: This guide was written from Vertafore's public developer documentation (a few details could not be confirmed) and has not been tried yet on a live Vertafore account. If a screen looks different from what is described, press Connect, then Download report, and send it to support. We fix it for everyone.
Who this is for: insurance claims. How Vertafore gives access: The vendor only gives API access after an approval or a business agreement. Ask them first (steps below); until then use the no-API options at the end. What it costs you: Not stated in the Developer Portal getting-started page; scopes reflect what your agency contracted for.
Part 1. Get your key from Vertafore
Do this on your computer, in a new browser tab, signed in to Vertafore.
- Sign in to the Vertafore Developer Portal with your VSSO account (your agency must be a registered Developer Portal customer).
- Create an application; this generates your OAuth credentials.
- Build and test in the Sandbox, enabling only read scopes for each API.
- Submit a support ticket to Vertafore Customer Support asking for promotion to Live with read-only access to policies and claims.
- Ask the same ticket which scopes your agency contract includes and what the base URL and token address are.
- Vertafore emails the contact address on the application when approved; paste the Client ID and secret into Speakvora.
WARNING: If Vertafore asks which permissions to give, tick only the read-only ones: read-only scopes for customers, policies and claims, if your contract includes them. Never give write or admin access.
TIP: To copy the key, click inside the box that shows it, press Command + C on a Mac or Ctrl + C on Windows (or right-click and choose Copy). Nothing will look different. It is now in your clipboard, ready to paste. Keep it private: anyone who has it can read your orders.
Part 2. Open the Connect tab in your agent
- Open your agent's dashboard (the page you open from the Start Speakvora Agent file).
- Press Connect in the menu. On a phone the menu is the bar along the top; slide it sideways if you do not see Connect.
- Under Your apps type Vertafore in the box that says Find an app (1), or scroll down the list.
- Press Vertafore AMS360. A card slides up. (If you only see apps for your own kind of business, that is on purpose: your agent only shows the systems that make sense for it.)



Part 3. Paste it in
2 boxes to fill in. Click inside a box, press Command + V on a Mac or Ctrl + V on Windows, then move to the next:
- Client ID. Shown on your application in the Vertafore Developer Portal after approval.
- Client secret (secret: it stays on this computer and is never shown again, only the last few characters). Shown once when the application credentials are created in the Developer Portal.

TIP: Pasted by mistake into the wrong box? Click the box, press Command + A (Ctrl + A on Windows) to select all, then paste again.
Part 4. Test it
- Press the orange Save and test button.
- Vertafore has no safe read-only check we can run, so nothing is called. The connection is used for real the first time a customer asks about an order, and any problem shows in Activity.

YOU SHOULD SEE: green words starting with Connected. (here: *Saved* and the sentence about the first customer)
WARNING: Red words mean it did not work yet. Read them, then see If something is wrong below. Nothing bad happened.
What happens next
- A customer texts something like where is order 1234. The agent answers *Your order 1234 is preparing.* (the status word from Vertafore), or *I could not find that order. A team member will check and reply.*
- Each person can ask five times an hour. If Vertafore is down, the conversation carries on and the problem is written to Activity.
- Mode: the agent asks Vertafore when a customer asks.
If something is wrong
- It says the key was refused (401 or 403): copy the key again from Vertafore. Make sure there is no space before or after it, and that it is a live key for the right shop or location.
- It cannot find an order (404): the number is not in Vertafore, or Vertafore uses a longer number than the one on the receipt.
- It says too many requests (429): wait a minute and press Save and test again.
- Vertafore says you need a plan or approval: Vertafore uses OAuth credentials and a Sandbox-to-Live promotion that Vertafore must approve through a support ticket. The getting-started page gives no base URL and no read-one-claim or test endpoint, so none is listed here rather than guessed. Claims endpoints are not confirmed.
- Still stuck? Press Connect, then Download report, and email it to support. It never contains keys or customer messages.
If your plan has no API
- Ask Vertafore support about the legacy Web Service API (Login ID and password created in AMS360 setup).
Vertafore's own instructions: https://help.vertafore.com/devportal/content/getstarted/gettingstarted.htm
All help guides · Every agent feature · AI receptionist by industry
Questions
What if this happens: It says the key was refused (401 or 403)?
copy the key again from Vertafore. Make sure there is no space before or after it, and that it is a live key for the right shop or location.
What if this happens: It cannot find an order (404)?
the number is not in Vertafore, or Vertafore uses a longer number than the one on the receipt.
What if this happens: It says too many requests (429)?
wait a minute and press Save and test again.
What if this happens: Vertafore says you need a plan or approval?
Vertafore uses OAuth credentials and a Sandbox-to-Live promotion that Vertafore must approve through a support ticket. The getting-started page gives no base URL and no read-one-claim or test endpoint, so none is listed here rather than guessed. Claims endpoints are not confirmed.
What if this happens: Still stuck??
Press Connect, then Download report, and email it to support. It never contains keys or customer messages.