Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/SpaceNeuroX/proxy-turn-vk-android/llms.txt

Use this file to discover all available pages before exploring further.

qWDTT accepts JSON objects as a portable profile format. A JSON profile is the same structure used inside .qwdtt files, inside subscription profile arrays, and in .conf file attachments sent by the server’s Telegram bot. You can hand-author a profile, export one from qWDTT, or receive one from a server admin — the import path is the same in all cases.

​
Schema

{
  "name": "My Server",
  "peer": "203.0.113.10:56000",
  "hashes": "hash1,hash2",
  "workers": 18,
  "port": 9000,
  "password": "MySecretPass16"
}

​
Field Reference

​
name
string
Display name for the profile shown in qWDTT’s profile list. Optional — if omitted, qWDTT assigns "Imported" as the default name.
​
peer
string
required
Server IP and DTLS port in ip:port format. Example: 203.0.113.10:56000. This is the address the Go client uses as -peer.
​
hashes
string
required
Comma-separated VK call join hashes (up to 4). Also accepted as vkHashes. If this field is blank or absent, qWDTT falls back to the global VK hashes pool configured in Settings.
​
workers
integer
Workers per hash. Also accepted as workersPerHash. Defaults to 16 if omitted. Recommended range: 16–27 for anonymous VK mode; 4 for VK account mode.
​
port
integer
Local UDP listen port on the Android device. Also accepted as listenPort. Defaults to 9000 if omitted.
​
password
string
required
Connection password. Also accepted as pass. The WRAP encryption key is derived from this value via HKDF.

​
Alternative Key Names

qWDTT accepts both canonical field names and legacy alternatives. This makes it compatible with configs authored for the original WDTT client.
CanonicalAlternative
hashesvkHashes
workersworkersPerHash
portlistenPort
passwordpass

​
Import Methods

1

Paste from clipboard

Copy a raw JSON object to your clipboard. When you open qWDTT, it detects JSON content and prompts you to import the profile.
2

Open a .qwdtt file

Tap a .qwdtt file in a file manager, email attachment, or messaging app. The file may contain a URI or a JSON object — qWDTT handles both.
3

Scan a QR code

Use qWDTT’s QR scanner to scan a code containing a raw JSON object or a Base64-encoded JSON string.
4

Receive from the Telegram bot

Ask the server admin to send a .conf file attachment via the server’s Telegram bot. Tap Open in qWDTT from the share sheet to import directly.
To import multiple profiles in one operation, wrap them in a JSON array: [{...}, {...}, ...]. qWDTT parses the array and creates all profiles at once, optionally placing them in a named folder if a groupName field is present on the first object.
QR codes and clipboard content can contain Base64-encoded JSON instead of raw JSON. qWDTT automatically detects and decodes Base64 payloads before parsing, so either encoding works for any import method.

Build docs developers (and LLMs) love

Get started for freeTalk to us