



Notion provides an all-in-one workspace combining notes, tasks, databases, wikis, and collaboration features, helping teams organise knowledge and work in one place.
Have any questions? We’re here to help You
All API requests require authentication via bearer token. After successfully connecting a system through Makini's authentication module, you receive an API token. Include this token in the Authorization header of your requests: `Authorization: Bearer YOUR_API_TOKEN`. Each connection has a unique token, allowing you to manage multiple customer connections independently. Tokens remain valid as long as the underlying system credentials are valid and the connection is active. If a customer changes their system credentials, you'll need to reconnect to obtain a new token.
Makini maintains a comprehensive data model built from analyzing thousands of industrial systems. When data flows through Makini, we automatically transform it from the source system's format into our standardized structure. For example, purchase orders from SAP, NetSuite, and Dynamics all return with consistent field names, data types, and structures. This normalization happens in real-time as data passes through the API. You also have access to raw data if needed for specific use cases. The unified model covers common entities like purchase orders, work orders, inventory items, vendors, and assets, with extensive field coverage across systems.
Industrial systems are often heavily customized, and Makini is built to handle this. For reading data, Makini can access virtually any field or custom table in connected systems. Through the connection settings interface, you can specify custom fields, tables, or entities to include in API responses. These show up alongside standard fields in the unified model. For custom objects not in our default model, you can request them through the interface and they'll be available immediately. For writing data, customization support varies by system but covers most common scenarios. During implementation, we work with you to identify required customizations and ensure they're properly configured before going live.
Yes, customers can connect as many systems as needed. Each connection is independent with its own API token, allowing you to manage multiple ERP systems, CMMS platforms, or other integrations for a single customer. This is common in organizations with multiple subsidiaries, regional systems, or during migration periods when legacy and new systems run in parallel. Each connection consumes connection credits based on the system type and deployment model. There's no technical limit on the number of connections per customer. For customers using multiple instances of the same system (like regional SAP instances), each instance requires a separate connection with its own credentials and token.
