Register an application in the Applied Dev Center at devcenter.myappliedproducts.com; obtain a client ID and client secret, then request a production application once sandbox testing is complete.
Authenticate using OAuth 2.0 to obtain a bearer token; include it as Authorization: Bearer YOUR_TOKEN in all subsequent requests.
Query client records via GET /clients to retrieve a paginated list; filter by client name or code and capture the clientId for downstream calls.
Retrieve policy summaries for a client via GET /clients/{clientId}/policies; each policy object includes policyNumber, lineOfBusiness, carrier, and term dates.
Pull contact details via GET /contacts/{contactId} and attachments via the Attachments API endpoint documented in the Applied Dev Center to gather COI or endorsement documents.
Write any external data back (e.g., claims updates, activity notes) using the appropriate POST/PATCH endpoints; consult the Dev Center for the current API version and available write operations for your Epic database version.
Known gotchas
Applied Epic API access requires the agency to enable API access on their Epic database and provide their enterprise ID; without this, authentication succeeds but data calls return empty or forbidden responses.
The API surface varies by Epic release version; an endpoint available in one version may not exist in an older on-premise database — confirm the database version against the Dev Center compatibility matrix before building.
Rate limits apply per application credential; bulk data extraction should use cursor-based pagination and back-off logic to avoid 429 errors.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp