Contact and support
Technical contact
Section titled “Technical contact”For technical questions, write to the MarsX technical contact:
The contact signs as Tim Teknis MarsX (MarsX Technical Team).
What to include
Section titled “What to include”- The
instancereference from the error, or therequest_idfrom the answer. MarsX uses it to find the exact cause in its own logs. - The connection reference, the
webhook-idand the event type. - Whether you used the sandbox or production.
Never send a signing key, a secret, a token, a lead file or any customer data in an email. Keys travel only through the one-time secure key exchange. Lead files travel only through the signed upload or the upload by staff account.
Incidents and maintenance
Section titled “Incidents and maintenance”MarsX tells you about API incidents and planned maintenance by email, from the technical contact address to your technical contact. MarsX has no status page.
Keys and the secure key exchange
Section titled “Keys and the secure key exchange”The issuer of a key or client credential shares it through a one-time, expiring secure share. MarsX emails the share link to your technical contact from the MarsX technical contact address. The access password and the SHA-256 fingerprint of the key are read out on a call. Sandbox and production use separate shares.
Security concerns
Section titled “Security concerns”If you think a key has been exposed, tell the technical contact at once. MarsX retires the old key at once on suspected exposure. See Change your key.
This site publishes a security.txt file at /.well-known/security.txt with the same contact.