Server time example

The smallest possible Custom Link round trip: ask the TMS for its current date/time. Use it to verify your endpoint URL and SOAP credentials before building a real integration. For the envelope mechanics and authentication see the SOAP overview.

Building this in n8n?

Using n8n with Custom Link walks through this exact command as its worked example — payload, envelope, the four-node workflow shape, and the response — and is importable as soap-server-time.json. This page covers the manual (curl) path only.

The payload

<?xml version="1.0" encoding="windows-1252"?>
<EoCustomLinkRequestDateTime Type="TEoCustomLinkRequestDateTime"/>

The envelope

The payload goes entity-escaped into the ARequest parameter of the single ExecuteRequest operation (how calls work):

<?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
  <SOAP-ENV:Header>
    <h:TAuthenticationHeader xmlns:h="urn:UCoSoapDispatcherBase">
      <UserName>YOUR_SOAP_NAME</UserName>
      <Password>YOUR_SOAP_PASSWORD</Password>
    </h:TAuthenticationHeader>
  </SOAP-ENV:Header>
  <SOAP-ENV:Body>
    <m:ExecuteRequest xmlns:m="urn:UCoSoapDispatcherCustomLink-ICustomLinkSoap">
      <ARequest xsi:type="xsd:string">&lt;?xml version="1.0" encoding="windows-1252"?&gt;&lt;EoCustomLinkRequestDateTime Type="TEoCustomLinkRequestDateTime"/&gt;</ARequest>
    </m:ExecuteRequest>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Call it

Save the envelope above as server-time.soap.xml (with your own credentials) and POST it:

curl "https://<your-client-name>.mendrix.cloud:5564/soap/ICustomLinkSoap" \
  -H 'Content-Type: text/xml; charset=utf-8' \
  -H 'SOAPAction: "urn:UCoSoapDispatcherCustomLink-ICustomLinkSoap#ExecuteRequest"' \
  --data-binary @server-time.soap.xml

Response

The result XML comes back entity-escaped inside return:

<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
  <SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
      xmlns:NS1="urn:UCoSoapDispatcherCustomLink-ICustomLinkSoap">
    <NS1:ExecuteRequestResponse>
      <return xsi:type="xsd:string">&lt;?xml version="1.0" encoding="windows-1252"?&gt;
&lt;EoCustomLinkResponseDateTime Type="TEoCustomLinkResponseDateTime"&gt;
 &lt;DateTime&gt;2026-07-22T12:40:13+02:00&lt;/DateTime&gt;
&lt;/EoCustomLinkResponseDateTime&gt;</return>
    </NS1:ExecuteRequestResponse>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Unescaped, the return payload is:

<?xml version="1.0" encoding="windows-1252"?>
<EoCustomLinkResponseDateTime Type="TEoCustomLinkResponseDateTime">
 <DateTime>2026-07-22T12:40:13+02:00</DateTime>
</EoCustomLinkResponseDateTime>

With wrong credentials you still receive an HTTP 200 SOAP response, but the return payload is a TEoCustomLinkException (ExceptionClassName: EWrongUserPassword) — see errors.