Skip to content

Introduction

Welcome to the MendriX Developer Portal — the central place to build integrations with the MendriX Transport Management System (TMS).

MendriX offers two integration surfaces:

REST APISOAP Custom Link (legacy)
StatusPrimary, actively extendedLegacy, maintained for specific flows
FormatJSONXML
AuthBearer JWT via login-api-tokenToken in the SOAP request
Best forClients, contacts, invoices, order updates, tasksOrder intake (StoreOrdersNormal)
ReferenceInteractive REST referenceSOAP overview

Use REST for everything it supports. The one flow that still requires SOAP today is creating orders (order intake). REST order creation is planned — it is marked coming soon throughout this portal. Do not build against REST order-creation endpoints until they appear in the REST API reference.

The REST API is organised into a few services:

  • Client — list, create, get, update and soft-delete clients; manage contacts, per-client address books and the global address book.
  • Invoice — list, get and patch invoices; finalize, cancel or delete preliminary invoices; list and record payments.
  • Order — patch orders and tasks, copy orders (including credit copies), and rank purchase options.

The SOAP Custom Link is used for order intake (StoreOrdersNormal) and related legacy operations.

Typical integrations built on top of these:

  • Client & CRM sync — keep your CRM and the TMS aligned in both directions.
  • Order intake — push orders from your own system into MendriX.
  • Order status & track-and-trace — receive status changes by webhook and fall back to polling.
  • Invoices → accounting — pull finalized invoices and post payments back.

Every integration guide documents each step twice, in a synced tab pair:

  • Manual (REST) — full curl and JavaScript examples.
  • n8n — a node-by-node walkthrough plus an importable workflow JSON.

Your tab choice is remembered site-wide, so if you pick n8n once you will see n8n instructions everywhere.

  1. Review your environments & URLs.
  2. Create a token and make your first call in Authentication.
  3. Follow Your first integration end to end.