MKG Exchange

Through the MKG API, data and processes can be linked in a structured manner. This enables the exchange of information, automation of processes, and integration of MKG into a broader digital landscape. For manufacturing companies, this means fewer standalone systems, less manual work, and more control over the digital workspace. To work with the MKG API, the MKG Exchange license is required.

The MKG ERP software has a continuous and regular release cycle in which the MKG API is also developed. New possibilities, API services, and releases can thus be actively included in the further development of the platform. In this way, the MKG API is a 'living' integration base that grows with the software and the practice of the manufacturing industry. Contact us for more information.

From Insight to Process Integration

The MKG API is the technical foundation that allows customers, partners, and developers to connect MKG with other systems, applications, and data sources. If you have an MKG Exchange license, you can read the entire MKG ERP system. Therefore, the API is not only suitable for reports, dashboards, data connections, and analyses, but almost all important processes can also be modified via creation, modification, and deletion. Thus, MKG Exchange supports not only insight but also real process integration.

One Uniform API Structure

The MKG Exchange license is part of a uniform API structure. Partners and developers work with a consistent base of endpoints and fields. This makes integrations scalable and better maintainable. A solution does not need to be reinvented per customer but can be developed on a recognizable technical basis.

Clear Frameworks

Goal-Oriented

API access must fit the purpose of the integration. A connection gets access to the data and functions needed for the agreed-upon goal.

Testing

New or modified integrations are first tested in an appropriate development or sandbox environment. Every MKG customer has their own sandbox environment by default. Additionally, partners have their own sandbox environment for development and testing. This way, we minimize risks before a connection is used in production.

Support

MKG supports the standard operation of the MKG API. Each owner of a connection, add-on, or custom solution is responsible for their own setup, logic, operation, and support towards the customer.

Performance

A good integration efficiently handles API traffic. Unnecessary polling, heavy synchronizations, broad exports, and incorrect retry logic can affect performance and should be avoided.

Security

Integrations can have access to company data, personal data, or process-critical information. Therefore, we look at what data is used, why that data is needed, and how API keys and access are managed.

What can you do with the MKG Exchange license? +-
  • Retrieve data from MKG.
  • Synchronize data with other (software) systems.
  • Feed reports and dashboards.
  • Support e-commerce or customer portals.
  • Connect document management, logistics, or calculation software.
  • Automate recurring processes.
  • Create, modify, or delete data within important MKG processes.

The exact possibilities depend on the available API functionality, the setup of the customer environment, the license, and the assessment of the intended use.

READ or CRUD? +-

With an MKG Exchange READ license, information from MKG can be read. This license is suitable for situations where data from MKG is used for reports, dashboards, analyses, external systems, or periodic exports. With an MKG Exchange CRUD license, information can not only be read, but data can also be created, modified, and deleted. This license is suitable for integrations where processes are actively linked or automated, such as synchronizations, customer portals, e-commerce, planning, logistics, or other process integrations.

What are the benefits for partners and developers? +-
  • Faster development
  • Simpler reuse
  • Less customer-dependent customization
  • Better maintainability
  • Scalable solutions for multiple MKG customers
Cloud or on-premise? +-

MKG makes no functional distinction between cloud and on-premise installations. The API base is the same. This means that integrations can be developed on the same functional basis, regardless of the environment in which the customer operates. For use in the MKG Cloud, we do assess the API usage more carefully. Because cloud environments can be shared, we look at performance, stability, error handling, and potential impact on other customers.

Developer page and self-support +-

For developers, there is a separate API developer environment available. This helps customers, partners, and developers to answer many questions themselves and better prepare integrations. To quickly and independently get started with the MKG API, you will find in our Knowledge Center elaborated API examples, status codes, Postman collections, frequently asked questions, explanations about error handling, practical guidelines, and additional technical documentation.

Interested in MKG Exchange? +-

Do you want to know more about connecting with MKG? Or do you want to apply for an MKG Exchange READ or CRUD license? Contact us. We will help you determine which license and route fit your integration request.