














































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