Integration into your IT environment | Communication with MetriXFreight REST-API

MetriXFreight has two different ways of communicating with other systems.

Variant A - Direct Reply: MetriXFreight receives a measurement request and sends the measurement directly back to the requesting system.
Variant B - Reply to Backend: MetriXFreight receives a measurement request and sends the result to another system defined by you in advance.

In both cases, you provide the components shown in green in the illustration below.
Both the response "http response" for variant A and the response for variant B are in the same format. (Click here for more information)

Variant A | Direct Reply

MetriXFreight receives a measurement request and sends the measurement directly back to the requesting system.
(MetriXFreight saves a raw data version in the background. This can be accessed in an emergency).

Example
You have a WMS system. The process starts with a request. The request for measurement is sent from your WMS system to MetriXFreight, e.g. by scanning a package number or typing in an EAN, etc. MetriXFreight measures and then sends the measured data back to the WMS system.
Your WMS system is the storage location for the measured data. This system does not have to be a server in variant A.

Handling barcode scanner

You have the option of purchasing a scanner from us. Alternatively, your existing scanners can also be integrated.

Variant B | Reply to backend

MetriXFreight receives a measurement request and sends the result to another system defined by you in advance.
The trigger for a measurement request and the recipient of the measurement data are located in different systems. However, they can communicate with each other independently of MetriXFreight.

Example
You have a WMS system and a TMS system. The measurement process starts with a request, for example from the WMS system. The request for measurement is therefore sent from your WMS system to MetriXFreight, e.g. by scanning a package number. MetriXFreight then measures and sends the measured data to your TMS system. The storage location of the measured data is your server (in the figure above: server of the TMS system). It must be programmed so that the data is received and stored correctly.

It is your responsibility to ensure that the measurement data is linked or enriched with your own data. MetriXFreight only saves a raw data version in the background. This can be accessed in an emergency.
Optional fields, such as additional notes, checkbox for air freight, stackability factor, ... can be added to the trigger message. These are then forwarded with the measurement results (For more information? -> Read the paragraph Format of the data - JSON message).

Handling Barcode Scanner

If you opt for variant B, we will provide you with a barcode scanner that is linked to the MetriXFreight system.
Alternatively, you can use our MetriXAssist Android app. The app is particularly recommended for measuring with ceiling systems. The measurement results are displayed directly on the portable scanner screen. This means your employees can see the results immediately and can evaluate and process them quickly and efficiently.

Data format | JSON message

The data is transmitted as a JSON message. Each JSON message contains:

ID & measurement data
Optional: Color images (base-64 encoded)
Optional: additional user input or fields (in the master data edition)
Optional: Optional user data (e.g. WMS ID) from the trigger source

It is possible to integrate MetriX measurements into any WMS/TMS/ERP system that supports REST interfaces. However, it is important that you implement the import of the measurements into your specific WMS/TMS system.

Please consult your MetriXFreight specialist in advance to determine the appropriate connection.