Skip to main content
Store the business intent, exact amount, login, request key and returned ID before marking an action completed in the CRM. A timeout can happen after MT5 has already executed a write.

​
Read a response

201 confirms account registration or creation, or a created allocation depending on the route. 202 means accepted for asynchronous processing. Follow GET /api/v1/mamx/operations/{operation_id} until terminal or until intervention is required; use bounded polling/backoff. PENDING and RUNNING are not completed. DONE confirms completion; inspect the operation-specific result. REJECTED is a rejection, not a reason for an automatic new financial request. REVIEW means evidence or execution is uncertain. For new account credentials use GET /api/v1/mamx/operations/{operation_id}/credentials after completion, with the broker key. Never record credentials in request traces. Imported accounts do not issue new passwords.

​
Retry contract by endpoint

401: check the bearer key and broker instance. 422: fix invalid fields, formats or incompatible inputs. 409: read the detail and the current operation/allocation. A conflicting idempotency key is not fixed by retrying with altered data. A pending close or PF may need to settle first. 503: check API configuration, schema and readiness. Do not switch to a fresh key just because the response was lost.

​
What to do in REVIEW

Stop automatic retries for that intent. Preserve the operation/task ID, login, amount, timestamps and any MT5 ticket. Send them to the operator, without credentials. The operator checks MT5 against the durable receipt, confirms the old worker is stopped, and only then may authorize recovery using the full documentation. This authorizes reconciliation, not an unconditional second debit or trade. Do not delete a receipt, reset a cursor or manually mark the operation DONE to clear the queue.