wiki/knowledge/crm-automation/cordwainer-eldermark-api-integration.md · 621 words · 2026-03-24

Cordwainer — Eldermark API Integration

Overview

Cordwainer Memory Care uses Eldermark as their CRM platform. The standard Eldermark UI lacks certain features needed to fully customize the system to Cordwainer's workflows. Gaining API access to the Eldermark backend would allow the team to programmatically interact with the CRM — adding, removing, or modifying data and behaviors that have no corresponding button or setting in the user interface.

This integration is a prerequisite for the broader CRM customization work planned for this client.

Current Status: Blocked — API access not yet secured as of 2026-03-24.

Why API Access Is Needed

The Eldermark UI does not expose all configuration options. Certain customizations — adding fields, removing elements, or adjusting backend behavior — require direct API interaction. As Karly explained in the 2026-03-24 meeting:

"What the API access will allow us to do is interact with the actual user interface without actually having to use the interface, because there's certain things like adding things here and there or removing things here and there that we want to do that they don't have a button on the user interface for us to actually do that… It's essentially allowing us to get into the back end and then recode some things to fit it exactly how we want it."

Integration History

Date	Event
Pre-2026-03-24	Bodo Liesenfeld (client) initiated contact with Eldermark; was routed to Omaima (Eldermark technical contact) as the person authorized to grant API access
Pre-2026-03-24	Omaima sent a system-generated API key with an expiration notice
Pre-2026-03-24	Karly attempted to use the API key and log into the Eldermark support portal; login failed
2026-03-24	Confirmed: API key has likely expired; support portal login still failing; phone number in Omaima's email signature is invalid
2026-03-24	Ownership transferred to Karly to lead the project going forward

Current Blockers

Expired API key — The key Omaima originally issued has likely expired before it could be used.
Portal login failure — Credentials used for the standard Eldermark CRM do not work on the separate support portal (different auth system).
Invalid contact phone — The phone number in Omaima's email signature returns a "not a valid number" error.
Communication gap — No recent inbound communication from Omaima; unclear whether she is still the right point of contact.

Key Contacts at Eldermark

Name	Role	Notes
Omaima	Technical contact; authorized to grant API access	Primary point of contact; phone number in signature is invalid
Krista	Customer Care Manager	Should be CC'd on all correspondence to ensure accountability and smooth escalation

Action Plan (as of 2026-03-24)

Owner: Karly Oykhman

Email Omaima — Request a direct phone call; provide Karly's phone number since Omaima's is non-functional.
CC Krista (Customer Care Manager) and Bodo Liesenfeld on all correspondence.
Follow up daily until access is confirmed.
Once API access is granted, implementation is expected to move quickly.

Technical Notes

Eldermark uses a separate support portal from the main CRM, with its own authentication system (email-based login vs. username-based login in the main system).
The API key is time-limited and must be used before expiration — coordinate promptly once a new key is issued.
Bodo is CC'd for visibility only; he is not a technical participant and defers entirely to Karly on the substance of these conversations.

^[1] — Cordwainer Memory Care client overview
^[2] — Source meeting where ownership was transferred to Karly