Skip to main content
The API must be consumed from a secure backend. The integrator maintains users, products, business limits, and permissions in its own source of truth; the ExuraCopy MAM API manages MAM accounts and their operational relationships.

​
Fields you should normally omit

  • user_id and metatrader_account_product_id: internal references for full-platform solutions; they are not CRM IDs.
  • payment_account_login when creating a new leader: omit it or send null to create the PAYMENT account automatically.
  • Reserved fields such as equity_limit, min_free_margin, copy_sl, copy_tp, and copy_existing_positions: they do not enable currently contracted behavior.
The presence of a field in Swagger does not mean you should send it. Send only the fields documented for the integration workflow.

​
Omitted fields, null, and empty strings

  • Omitting an optional field allows its default value to apply.
  • Sending null is valid only when the field contract explicitly allows it.
  • An empty string is not equivalent to omission and normally produces 422 for names or logins.
  • For numeric fields, 0 is a real value; it does not mean “no value.”

​
Security rule

Do not expose the API key, MT5 credentials, payment_account_login, or signing_secret in frontends, mobile applications, public logs, or analytics tools.

​
Continue

Previous: Overview

Review the concepts and identifiers that the integrator must retain.

Next: Authentication and environments

Configure the base URL, API key, and headers for each request.
Last modified on November 3, 2026