M

mx.com

8 integrations · REST

MX exposes multiple HTTP APIs—Platform API (OpenAPI), Data Enhancement Off Platform, MDX Real Time, MDX On Demand v5, Migration, Reporting, legacy Nexus and Atrium, plus a Batch SFTP interface—with auth primarily via Client Dashboard-issued `client_id` + `api_key` (Basic auth for Platform, `MD-API-KEY` plus `client_id` in path/query for several legacy APIs), Nexus session tokens from SSO, MX-provisioned Batch SFTP credentials, and MX-provisioned HMAC keys for MDX On Demand.

discovered 2mo ago
REST · OpenAPI8
Credentials
MX client ID + API keybasicGet credentials ↗

Sign in to the Client Dashboard. Under Client Dashboard, use Manage API Keys to view/copy/rotate your development and production API keys, and note your client_id from the dashboard. MX docs state these values can be used with Basic auth for the Platform API, with client_id as the username and api_key as the password. Many legacy APIs also require the same api_key in an MD-API-KEY header and the client_id in the base URL or query string. Whitelist your source IPs in the dashboard before calling IP-restricted APIs.

MDX On Demand HMAC keysignature

For MDX On Demand v5, MX provides a shared HMAC key during partner integration. Your implementation must verify MDX-HMAC and Content-MD5 headers on requests from MX, and use the session flow described in the docs. The key is provided by MX in base64 and supports HMAC SHA1/SHA224/SHA256/SHA384/SHA512.

conventions · 1/8 published

Publish these signals → /publishing