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

# Get available VASPs

> Retrieve the list of Virtual Asset Service Providers (VASPs) for travel rule submissions via the V4 API.

## Overview

This endpoint retrieves the list of VASPs that can be used when submitting travel rule data for deposits and withdrawals. For detailed Travel Rule requirements, see [Travel Rule](/concepts/travel-rule).

**When to use `vaspId` vs `vaspName`:**

* If the destination/originating VASP appears in this list, use its `vaspId` for accurate identification
* If the VASP is not in the list, use `vaspName` as a fallback with the VASP's name as a string

***

## Usage Notes

<Note>
  The list may vary depending on the account's region.
</Note>

***

## VASP Selection Flow

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
sequenceDiagram
    participant Client
    participant WhiteBIT API

    Client->>WhiteBIT API: POST /api/v4/travel-rule/vasps
    WhiteBIT API-->>Client: List of available VASPs

    Note over Client: Search for target VASP in list

    alt VASP found in list
        Note over Client: Use vaspId from response
        Client->>WhiteBIT API: Submit with { vaspId: "vasp-001" }
    else VASP not in list
        Note over Client: Use vaspName as fallback
        Client->>WhiteBIT API: Submit with { vaspName: "Famous Vasp Name" }
    end
```

***

## Related

* [Submit deposit verification](/api-reference/travel-rule/submit-deposit-verification) — Use VASPs when submitting deposit originator data
* [Create withdraw request](/api-reference/account-wallet/create-withdraw-request) — Use VASPs when creating withdrawals with travel rule data
* [Travel Rule](/concepts/travel-rule) — Detailed requirements and workflows


## OpenAPI

````yaml openapi/private/main_api_v4.yaml POST /api/v4/travel-rule/vasps
openapi: 3.0.3
info:
  title: WhiteBIT Private HTTP API V4
  description: |
    WhiteBIT Private HTTP API V4 for Main balance changes.

    Base URL: https://whitebit.com

    All endpoints return time in Unix-time format.
    All endpoints return either a JSON object or array.
    For receiving responses from API calls please use http method POST.
  version: 4.0.0
  contact:
    name: WhiteBIT Support
    email: support@whitebit.com
    url: https://whitebit.com
servers:
  - url: https://whitebit.com
    description: WhiteBIT Global Server
  - url: https://whitebit.eu
    description: WhiteBIT EU Server
security:
  - ApiKeyAuth: []
    PayloadAuth: []
    SignatureAuth: []
tags:
  - name: Main Account
    description: Main account balance and operations
  - name: Deposit
    description: Cryptocurrency and fiat deposit operations
  - name: Withdraw
    description: Cryptocurrency and fiat withdrawal operations
  - name: Transfer
    description: Balance transfer operations
  - name: Codes
    description: WhiteBIT codes operations
  - name: Crypto Lending - Fixed
    description: Fixed crypto lending plans
  - name: Crypto Lending - Flex
    description: Flexible crypto lending plans
  - name: Fees
    description: Fee information
  - name: Sub-Account
    description: Sub-account management
  - name: Sub-Account API Keys
    description: Sub-account API key management
  - name: Mining Pool
    description: Mining pool operations
  - name: Credit Line
    description: Credit line information
  - name: JWT
    description: JWT token management
  - name: Travel Rule
    description: Travel Rule compliance endpoints for deposits and withdrawals
paths:
  /api/v4/travel-rule/vasps:
    post:
      tags:
        - Travel Rule
      summary: Get available VASPs
      description: >
        Retrieves the list of Virtual Asset Service Providers (VASPs) that can
        be used when submitting travel rule data for deposits and withdrawals.


        Use the returned `vaspId` when submitting travel rule data if the
        destination/originating VASP is in this list. If the VASP is not in the
        list, use `vaspName` as a fallback.


        <Accordion title="Errors">

        **API disabled for region (422):**

        ```json

        {
          "code": 0,
          "message": "Something went wrong",
          "errors": {
            "error": ["This endpoint is disabled for your region"]
          }
        }

        ```

        </Accordion>


        Beyond the errors above, this endpoint can return only the [common
        authentication errors](/api-reference/authentication).


        <Warning>

        Rate limit: 1000 requests/10 sec.

        </Warning>
      operationId: getTravelRuleVasps
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - request
                - nonce
              properties:
                request:
                  type: string
                  description: Request signature
                  example: '{{request}}'
                nonce:
                  type: integer
                  description: Unique request identifier
                  example: 1594297865000
      responses:
        '200':
          description: Successful response with list of VASPs
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      vasps:
                        type: array
                        items:
                          type: object
                          properties:
                            vaspId:
                              type: string
                              description: >-
                                Unique VASP identifier to use in travel rule
                                submissions
                              example: vasp-001
                            name:
                              type: string
                              description: Human-readable VASP name
                              example: Binance
              example:
                data:
                  vasps:
                    - vaspId: vasp-001
                      name: Binance
                    - vaspId: vasp-002
                      name: Coinbase
                    - vaspId: vasp-003
                      name: Kraken
        '422':
          description: API disabled for region
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                code: 0
                message: Something went wrong
                errors:
                  error:
                    - This endpoint is disabled for your region
components:
  schemas:
    Error:
      type: object
      properties:
        code:
          type: integer
        message:
          type: string
        errors:
          type: object
          additionalProperties:
            type: array
            items:
              type: string
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-TXC-APIKEY
      description: The public WhiteBIT API key.
    PayloadAuth:
      type: apiKey
      in: header
      name: X-TXC-PAYLOAD
      description: Base64-encoded JSON request body.
    SignatureAuth:
      type: apiKey
      in: header
      name: X-TXC-SIGNATURE
      description: >-
        HMAC-SHA512 signature of the payload, hex-encoded. Computed as
        hex(HMAC-SHA512(payload, api_secret)).

````