eWarehousing Solutions Middleware

eWarehousing Solutions eWMS middleware

The eWarehousing solutions middleware makes use of the JSON format. Authentication to the API is performed using a JWT token.

There are 2 mandatory headers that almost every request needs to have!

The X-Wms-Code header is always required and defines what eWMS system you want to communicate with.

The X-Customer-Code is always required unless you are logging in. This defines for which customer inside an eWMS you create orders etc..

When receiving data from an eWMS it's by default not sending all data back to the requester. For example:

When creating an order you won't receive back the address model and the order model.

If you do need the address and/or the orderline model. You can ask that by using the Expand header.

model	default	options
article	article, variants
batch	batch	inbound variant
inbound	inbound	inbound_lines variant
modification	modification	modification_lines variant
order	order	order order_lines variant shipping_address shipping_method documents
shipment	shipment	shipment_lines shipment_labels shipping_address shipping_method serial_numbers variant
shipping_method	shipping_method
stock	-
variant	variant	article

Webhooks use by default all expand headers!

Every get collection route can use the following filters:

AUTHORIZATIONBearer Token

Token