> ## Documentation Index
> Fetch the complete documentation index at: https://api-trading-docs.vexprofx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Validate the integration

> A test workflow for checking queries, opening orders, and closing positions.

Use a dedicated demo account and a token with the agreed permissions. Confirm the
symbol specifications and that the provider has enabled trading for the test.
You do not need to install or administer the server to consume the partner API.

| Step | Expected check |
| - | - |
| Query `/health/live` and `/health/ready` | API and MT5 connection available |
| Query your own account before verification | Access rejected |
| Verify with the master password | `valid:true`, `verified:true`, expiration date |
| List verifications | Binding for your token and login |
| Query account, positions, count, and orders | Consistent data; pagination respected |
| Query symbol ticks | Price available and parameters agreed |
| Store intent and key; submit demo opening order | Response stored and MT5 ID identified |
| Query result | Execution or rejection confirmed and reconciled |
| Query position | Actual ticket and volume identified |
| Submit close with a different key | New request ID |
| Query result and position | Close confirmed and position reduced or absent |
| Revoke verification | Access removed, with no pending trades left to manage |

Do not repeat incorrect passwords to trigger a lockout in a shared environment.
Test network failures and retries using client simulations before using them with
real trades. Check that an uncertain result does not trigger a second order with a new key.

In a controlled test, you can also verify that repeating an intent that already
received a response, using the same key and body, returns the stored response.
Do this only while the token and account remain authorized. Do not use another key for this test.

Do not approve the integration solely because POST requests return HTTP 200:
the criterion is the broker's result and its verified effect on the account.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.