
























































































AMTdirect (now part of MRI Software) is a real estate and facility management software for managing leases, properties, work orders, and capital projects.
Have any questions? We’re here to help You
Some editions of AMTdirect CAFM expose an API, but it is often limited, legacy, or inconsistent between versions, and many on-prem deployments have no usable API at all. Makini gives you one modern REST API for AMTdirect CAFM that lets you read and write AMTdirect CAFM data, even for legacy or on-prem instances. You build against Makini once instead of integrating with AMTdirect CAFM directly.
You integrate AMTdirect CAFM through Makini's Unified API. Authenticate once and Makini normalizes AMTdirect CAFM data into a single consistent schema you can read from and write to inside your product. The same connection reaches AMTdirect CAFM plus 2,000+ other ERP, WMS and CMMS systems, so you build one integration instead of one per system.
Through Makini you can read and write AMTdirect CAFM's core records as normalized, standardized resources, in both directions: pull data out of AMTdirect CAFM and push updates back in. Every field is mapped to a consistent Makini schema, so you work with the same object model across AMTdirect CAFM and every other connected system.
Days, not quarters. Because Makini already builds and maintains the AMTdirect CAFM connector, you do not reverse-engineer the integration yourself: you authenticate and start reading and writing AMTdirect CAFM data through the Unified API, typically within a few days. A AMTdirect CAFM integration built in-house usually takes months plus ongoing maintenance.
Yes. Makini connects to AMTdirect CAFM over encrypted connections on SOC 2 Type II certified infrastructure, and handles AMTdirect CAFM credentials for you so they are never exposed to your app. You authenticate once, and access runs through Makini's managed, auditable layer. The same security model applies across AMTdirect CAFM and every other connected system.
Makini owns the maintenance. When AMTdirect CAFM changes its API, versions, or endpoints, Makini updates the connector, and your integration keeps working with no changes on your side. You get a stable Unified API with webhooks, and AMTdirect CAFM upkeep stays off your roadmap.
