Build an integration against Applied Epic agency management data using the Applied Dev Center RESTful APIs
domain: devcenter.myappliedproducts.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register on the Applied Dev Center to explore available APIs, generate sandbox credentials, and review documentation
Decide whether to build on the newer RESTful APIs or migrate an existing integration from the legacy Applied Epic SDK (SOAP/WCF), since Applied documents a rewrite path between the two
Use the Attachments API for document data and/or the Contacts API for centralized client, prospect, and carrier contact data, depending on the integration's need
Build and test in the sandbox, then submit a production-application request including name, email, organization name, enterprise ID, and Epic database name
Wait for approval and email notification before production credentials become usable
Known gotchas
Production access requires an explicit manual approval step tied to your specific enterprise ID and Epic database name — it is not self-serve the way sandbox access is
Legacy SOAP/WCF Epic SDK integrations are being superseded by the RESTful APIs; confirm which generation of API a given tutorial or partner reference actually targets
API access is scope-gated per application — a dev account does not automatically have every available API enabled
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?