> ## 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.

# Integration permissions

> Access by route, verified account, and request ownership.

Request only the permissions you need. This table describes the capabilities the
provider must enable; these are not token issuance commands.

| Process | Method and route |
| - | - |
| Check MT5 | `GET /health/ready` |
| Verify ownership | `POST /api/v1/accounts/{login}/verify` |
| List verifications | `GET /api/v1/account-verifications` |
| Revoke verification | `DELETE /api/v1/account-verifications/{login}` |
| Query ticks | `GET /api/v1/market/ticks` |
| Query account | `GET /api/v1/accounts/{login}` |
| Query positions | `GET /api/v1/accounts/{login}/positions` |
| Count positions | `GET /api/v1/accounts/{login}/positions/count` |
| Query active orders | `GET /api/v1/accounts/{login}/orders` |
| Open a trade | `POST /api/v1/orders/market` |
| Place a pending order | `POST /api/v1/orders/pending` |
| Close a position | `POST /api/v1/positions/{position}/close` |
| Query result | `GET /api/v1/trading/requests/{request_id}` |

In addition to route permission, each account query and trade checks that the
verification for the token/login pair is active. You cannot query the result of
a request submitted with another token, even if both tokens verified the same login.
Opening and closing also require trading to be enabled by the provider.

See [authentication](/authentication) and [verifications](/accounts-passwords)
to distinguish a valid token from an authorized account.


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