














































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