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

# Revoke verification

> Remove your token’s access to the specified account.

## What this operation does

Returns `revoked:true` if it changes a revocable binding, or `revoked:false` if none existed. It does not close positions, cancel orders, or change the password.

## Complete workflow

See [the step-by-step guide](/accounts-passwords) and [errors and their handling](/errors).

Playground values are examples. Replace the account, symbol, volume, and price with valid data for your integration.


## OpenAPI

````yaml openapi.json DELETE /api/v1/account-verifications/{login}
openapi: 3.1.0
info:
  title: MT5 API — Partner Portal
  description: >-
    Secure endpoints for account ownership verification, market data, and
    trading on previously verified accounts.
  version: 0.1.0
servers:
  - url: https://api-trading.vexprofx.com
    description: API Trading · Partners
security: []
paths:
  /api/v1/account-verifications/{login}:
    delete:
      tags:
        - Accounts
      summary: Revoke an account verification
      operationId: revoke_account_verification_api_v1_account_verifications__login__delete
      parameters:
        - name: login
          in: path
          required: true
          schema:
            type: integer
            title: Login
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                type: object
                additionalProperties:
                  type: boolean
                title: >-
                  Response Revoke Account Verification Api V1 Account
                  Verifications  Login  Delete
        '422':
          description: Invalid request or incompatible closing parameters.
          content:
            application/json:
              schema:
                type: object
                required:
                  - detail
                properties:
                  detail:
                    type: string
              example:
                detail: Invalid request
      security:
        - HTTPBearer: []
components:
  securitySchemes:
    HTTPBearer:
      type: http
      scheme: bearer
      description: >-
        Send the provider-issued token in the Authorization header using Bearer
        authentication.

````

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