API Management

API Management

Speed up your API development and bring your integration landscape to the next level

Het eMagiz platform levert krachtige API management oplossingen en stelt hierbij alle functies van een API gateway beschikbaar.

What is an API gateway?

Where organizations previously used monolithic systems, they are increasingly moving their applications toward the cloud. As a result, data is increasingly decentralized and distributed. Information is literally scattered across different networks and this has major implications for the way data is exchanged.

In a landscape full of microservices, API gateways are often used as an intermediate layer between different applications and consumers. An API gateway can be used to provide access to information from different applications and systems and is used to standardize and manage communication between these systems. The API gateway of the eMagiz platform allows you to access services regardless of the protocol and takes into account security, throttling and versioning, among other things.

Why an API gateway with eMagiz?

Enrichment of data

Faster time-to-market for development teams and consuming applications as data streams can be handled in a unified manner

Increase reusability of endpoints and data

Improved manageability through standard access and security management

Easily and reliably exchange and transform data to any format or protocol


The eMagiz platform supports OpenAPI 3.0 and displays the details of an API operation in a Web portal using a SwaggerUI. The API gateway of eMagiz publishes a schema of data or operations made available and the parameters required to do so. Through a published website, a REST Web service is made accessible to authenticated users, which expects and returns JSON formatted messages.

Messages are processed synchronously on the front end via the published URL with guaranteed delivery and response. On the backend operations, transformations can be realized to enable certain content or protocol connections. This makes it possible to make data accessible via a different protocol, for example for the benefit of legacy on-premises systems or other data sources. In doing so, the API Gateway provides a transparent connection for end users and hides the complexity behind certain backend operations.

In terms of security, eMagiz offers a variety of options to authenticate users using API keys, OAuth2.0 or other alternatives. API callers are managed in the API Gateway, both at the backend operator level and/or at the data level, so that they can be provided with the appropriate authorization.

Hybrid use of integration patterns

The eMagiz iPaaS is capable of using the integration patterns Messaging, API gateway and event streaming in a hybrid way. This provides a unified user experience and a single interface in which developers can work. For example, within eMagiz it is possible to use an API gateway for synchronous API operations and then redirect the request to an asynchronous stream to communicate with legacy systems. It is also possible to process and synchronize real-time data between different services and then use an API gateway to provide a unified interface for retrieving that data. 

An API gateway usecase

Farm trans is a full-service logistics provider focused on food transportation. With the API gateway, Farm Trans has easily implemented the OTM data model, a standard for data exchange in the logistics sector. As a result, they are now able to link faster with supply chain partners, have the ability to transform data to any format or protocol, and now have significantly lower error rates and costs due to this digitization. Read how the eMagiz API gateway has contributed to lower development costs, easier & more efficient information exchange and more transparency to customers.

API gateway in a nutshell


Synchronous vs. asynchronous traffic

Synchronous traffic refers to data traffic where a response to the initial message is required. This means that the receiver of the message immediately responds and informs about the processing of the message and/or request. This is applicable, for example, in a production process where the process cannot start until sent message (for example, an order) is accepted by the receiving system.

Asynchronous traffic refers to data traffic where a response to the initial message is not required. The sending system can send data to the receiving system and an immediate response is not required. An example of asynchronous data traffic is uploading files to a cloud, where the sender uploads a file and the receiver can download and view files at a later time. 

Both types of traffic are supported in the eMagiz platform.