Retrieve agency policy and customer data from AMS360 using the Vertafore Developer Portal API
domain: vertafore.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create an application in the Vertafore Developer Portal and generate OAuth credentials for AMS360 API access
Enable the required AMS360 APIs and scopes for the application in the portal's API Catalog
Authenticate with OAuth and follow the documented tutorial flow (create header, then retrieve customer data) to validate connectivity
Use the AMS360 OData connection method for bulk/read-heavy policy data access where applicable
For legacy integrations, note that the older Web Service API (WSAPI) uses a WCF-based interface distinct from the newer OAuth REST APIs
Confirm the client agency is separately subscribed through Vertafore to the OData connection method before relying on it
Known gotchas
AMS360 exposes multiple integration mechanisms (OAuth REST APIs, OData, and legacy WCF-based WSAPI) that are not interchangeable -- pick the one matching your data needs rather than assuming WSAPI docs apply to the newer REST catalog
OData access must be separately subscribed to through Vertafore per client agency; it is not automatically available just because an application is registered in the Developer Portal
APIs and scopes must be explicitly enabled per application in the portal before calls succeed, even after OAuth credentials are issued
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?