Environments & URLs

MendriX is multi-tenant: each customer has its own hostname. Your base URLs are derived from your client name, which you receive during onboarding.

Throughout this portal, replace <your-client-name> with your own value.

REST API

https://<your-client-name>.api.mendrix.cloud/api

All REST paths in the API reference are relative to this base. For example, listing clients is:

GET https://<your-client-name>.api.mendrix.cloud/api/client/clients/

• Protocol: HTTPS only.
• Content type: application/json for request and response bodies.
• Authentication: Authorization: Bearer <access-token> — a short-lived JWT obtained via POST /account/login-api-token; see Authentication.

Custom Link (SOAP)

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

The SOAP endpoint listens on port 5564; its WSDL is published at https://<your-client-name>.mendrix.cloud:5564/wsdl/ICustomLinkSoap. It is used mainly for order intake. See the SOAP overview for connection details.

A note on client names

<your-client-name> is a fixed, lowercase identifier assigned by MendriX. If you are unsure of yours, ask your MendriX contact or the administrator who set up your API token. The same client name is used for both the REST and SOAP hostnames.

Keep the base URL configurable

Store the base URL as a single configuration value in your integration (an environment variable, an n8n credential, etc.) rather than hard-coding it. That keeps the move between a test tenant and production to a one-line change.

No separate sandbox host today

There is no public shared sandbox tenant. Test tenants, when provided, follow the same URL scheme with a different client name. Coordinate test access with your MendriX contact.