














































OZ e-Form is an electronic form and mobile data capture platform for inspections, work orders, and field workflows, integrating with backend maintenance and operations systems.
Have any questions? We’re here to help You
Some editions of OZ E-Form 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 OZ E-Form that lets you read and write OZ E-Form data, even for legacy or on-prem instances. You build against Makini once instead of integrating with OZ E-Form directly.
You integrate OZ E-Form through Makini's Unified API. Authenticate once and Makini normalizes OZ E-Form data into a single consistent schema you can read from and write to inside your product. The same connection reaches OZ E-Form 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 OZ E-Form's core records as normalized, standardized resources, in both directions: pull data out of OZ E-Form and push updates back in. Every field is mapped to a consistent Makini schema, so you work with the same object model across OZ E-Form and every other connected system.
Days, not quarters. Because Makini already builds and maintains the OZ E-Form connector, you do not reverse-engineer the integration yourself: you authenticate and start reading and writing OZ E-Form data through the Unified API, typically within a few days. A OZ E-Form integration built in-house usually takes months plus ongoing maintenance.
Yes. Makini connects to OZ E-Form over encrypted connections on SOC 2 Type II certified infrastructure, and handles OZ E-Form 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 OZ E-Form and every other connected system.
Makini owns the maintenance. When OZ E-Form 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 OZ E-Form upkeep stays off your roadmap.
