Register an application in the Vertafore API Developer Portal and use OAuth-authenticated AMS360 APIs to exchange agency management data
domain: help.vertafore.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Sign in to the Vertafore Developer Portal with a VSSO account, which requires being a registered, licensed Developer Portal customer
Create an application under My Applications to generate API Keys and OAuth Credentials
Enable only the specific API(s) and scopes your agency has contracted with Vertafore to use, since scopes are individually assigned, not universally available
Use OAuth Credentials, not the API-key credential type, for AMS360 application development, per Vertafore's explicit guidance
Test in the Sandbox environment, then promote the application to Live, which activates only the scopes actually exercised in Sandbox
Known gotchas
AMS360 developers must use OAuth Credentials specifically; the separate API-key credential type is documented as being for a different (forthcoming Rating API) use case
Enabling an API does not grant every scope under it — each scope must be individually toggled on, and requesting an unauthorized scope returns an explicit rejection message
Promoting an application to Live only activates the scopes actually used in Sandbox testing — untested scopes don't automatically carry over
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?