Overview & connection

The SOAP Custom Link is the legacy XML integration surface of the MendriX TMS. Prefer the REST API for everything it supports; use SOAP where it is still required — today that means order intake.

When to use SOAP

Use SOAP for	Use REST for
Order intake (StoreOrdersNormal)	Clients, contacts, address books
Legacy flows already built on Custom Link	Invoices & payments
	Order & task updates (PATCH), copies

REST order creation is coming soon; until it ships, new orders go through SOAP.

Endpoint & WSDL

SOAP requests are POSTed to the service endpoint:

https://<your-client-name>.mendrix.cloud:5564/soap/ICustomLinkSoap

The service contract (WSDL) is published separately at:

https://<your-client-name>.mendrix.cloud:5564/wsdl/ICustomLinkSoap

• Port 5564, HTTPS.
• The service interface is ICustomLinkSoap; fetch the WSDL from the URL above to generate a client, or craft SOAP requests by hand and POST them to the service endpoint.
• Replace <your-client-name> with your client name (environments).

Data structures

All payloads are described by the XML schema GdxEoStructures.xsd. Key types for order intake:

• TEoCustomLinkStoreOrdersNormal — the store-orders request wrapper.
• TEoOrderMxList / TEoOrderMx — the order(s) to store.
• TEoTaskMxList / TEoTaskMx — the tasks (pickup, delivery, …) on an order.
• TEoAddress, TEoDateTimeWindow — addresses and time windows.

New vs existing records

An Id inside a TEoKeyIntInfraMx_NoData key uses a negative value to request insertion of a new record and a positive value to update an existing one. ClientNumber is resolved to a ClientId automatically when ClientId is not supplied.

Authentication

The Custom Link expects the API token to be supplied with the SOAP request. The exact placement (SOAP header vs transport auth) is configured for your tenant during onboarding. Use the token created in the TMS Api Tokens tab (authentication) and confirm the precise mechanism with your MendriX contact.

Placeholders only

All examples use obvious placeholders such as YOUR_API_TOKEN and <your-client-name>. Never commit real tokens.

Conventions

• Content-Type: text/xml; charset=utf-8.
• SOAPAction: the operation name (e.g. StoreOrdersNormal).
• Batching: TEoOrderMxList accepts multiple orders per call (up to the schema’s list maximum) — batch where possible instead of one call per order.
• Validation: validate outgoing XML against GdxEoStructures.xsd before sending.

Next

• Walk a complete request/response in the order intake example.
• See the workflow-oriented Order intake guide for the manual and n8n paths.