
























































































RefMan is a ship repair management system designed to help maritime operators control the full docking and maintenance process. It supports defect recording and monitoring, specification creation, contractor and shipyard bid comparison, cost control and reporting, progress and time tracking, yard performance evaluation, and documentation of drawings and job references.
Have any questions? We’re here to help You
Some editions of Refman 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 Refman that lets you read and write Refman data, even for legacy or on-prem instances. You build against Makini once instead of integrating with Refman directly.
You integrate Refman through Makini's Unified API. Authenticate once and Makini normalizes Refman data into a single consistent schema you can read from and write to inside your product. The same connection reaches Refman 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 Refman's core records as normalized, standardized resources, in both directions: pull data out of Refman and push updates back in. Every field is mapped to a consistent Makini schema, so you work with the same object model across Refman and every other connected system.
Days, not quarters. Because Makini already builds and maintains the Refman connector, you do not reverse-engineer the integration yourself: you authenticate and start reading and writing Refman data through the Unified API, typically within a few days. A Refman integration built in-house usually takes months plus ongoing maintenance.
Yes. Makini connects to Refman over encrypted connections on SOC 2 Type II certified infrastructure, and handles Refman 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 Refman and every other connected system.
Makini owns the maintenance. When Refman 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 Refman upkeep stays off your roadmap.
