Integration into systems that resist integration
A well-documented REST API is the easy case, and it isn't the case we're usually in. The systems that hold the data you need — HR, dental practice management, ERP, telephony — were built to run a business, not to be integrated with. Across three production deployments of TA LifeCycle Manager, here is the specific set of systems and protocols we've had to work against.
HR
UKG Pro, UKG Ready, and ADP Workforce Now — three different HR systems of record across three client deployments, each read on that vendor's own terms. Those terms differ more than a procurement checklist suggests: ADP Workforce Now holds an integrator to a materially stricter standard than either UKG product does, and meeting it is work you do once per vendor and never get to reuse.
Practice management
Denticon, Dentrix Enterprise, Dolphin and Cloud9. Denticon has no write API at all. Cloud9's API is deprecated. Dentrix Enterprise's data lives inside c-treeACE internals no vendor documents publicly. Where there's no API to call, provisioning steps against these systems go through a verified manual path and are confirmed automatically afterwards, as described on employee identity lifecycle.
ERP
NetSuite, worked from the inside: SuiteScript for logic that has to run inside NetSuite's own execution context, SuiteQL for reporting and joined reads across records, and SDF (the SuiteCloud Development Framework) for deploying and versioning that customization like real source code instead of clicking through the UI.
Telephony
RingCentral, provisioned and de-provisioned as part of the same HR-driven workflow that handles every other system — a phone extension gets created on hire and removed on termination without a separate ticket to the phone vendor.
The Microsoft estate
Hybrid Active Directory synced to Entra ID; M365 license assignment tied to role; Intune for device management; Defender for endpoint protection. This is the layer every other integration ultimately has to reach, because it's what actually turns an HR event into a working account, mailbox and set of licenses on someone's first day — and removes them cleanly on their last.
If your system isn't on this list
It's still worth the conversation — every system above started as a system with no documented way in. Tell us what you're trying to connect and what you've already ruled out. Send us the details, or book a call to talk through what integrating it would take.