XML Schema Definition.xsd

The XML schema GdxEoStructures.xsd defines every data structure used by the SOAP Custom Link — orders, tasks, addresses, invoices, rides and more. Use it to generate types, validate outgoing XML, and look up the exact fields for each structure.

Download

• GdxEoStructures.xsd — the complete schema.

Using the schema

• Validate before you send. Validate your StoreOrdersNormal (and other) payloads against this schema to catch structural errors locally.
• Generate types. Feed it to your SOAP/XML tooling (e.g. xsd.exe, wsimport, or a code generator) to produce strongly-typed classes.
• Look up fields. Each type carries <xs:documentation> describing its elements — search the file for a type name such as TEoOrderMx or TEoTaskMx.

Key types for order intake

Type	Purpose
TEoCustomLinkStoreOrdersNormal	Wrapper for the store-orders request
TEoOrderMxList / TEoOrderMx	The order(s) to store
TEoTaskMxList / TEoTaskMx	Tasks on an order (pickup, delivery, …)
TEoAddress	An address (name, street, postcode, place, country)
TEoDateTimeWindow	A DateTimeBegin / DateTimeEnd time window
TEoKeyIntInfraMx_NoData (written on the wire as Type="TEoKeyIntInfraMx")	Record key; negative Id = insert, positive = update

Keep the schema in sync

This file is served byte-for-byte from the repository. When MendriX ships an updated schema, replace it and the download link updates automatically — see the repository README’s maintenance notes.

Commands not in this schema

Three implemented Custom Link commands (StoreGlsLabels, StoreGlsUniboxTags, StoreDpdData) are absent from this schema and are internal carrier-middleware paths — see the Command reference for details. They are not supported integrator commands.

See the order intake example for a complete request/response built from these types.