VLESS Endpoints

VLESS protocol tunnel management including client connections, REALITY camouflage, and user provisioning on OrbMesh servers.

Connect (Client)

Establishes a VLESS tunnel connection. The server assigns a VLESS UUID and returns the connection parameters including REALITY camouflage settings for DPI evasion.

POST/vless/connect

Establish a VLESS tunnel connection with REALITY camouflage configuration

Authentication:Bearer Token

Device Token Required

This endpoint requires a device token obtained from OrbNET's device authorization flow. See the OrbMesh Authentication section for details.

When to Use VLESS

VLESS is ideal when WireGuard UDP traffic is blocked. It operates over TCP/TLS and uses REALITY to make the connection appear as legitimate HTTPS traffic to a well-known domain (e.g., www.microsoft.com), making it highly resistant to deep packet inspection.


Code Examples

curl -X POST https://198.51.100.1:8443/vless/connect \
  -H "Authorization: Bearer DEVICE_TOKEN" \
  -H "Content-Type: application/json"

Response

200VLESS connection established successfully
{
  "success": true,
  "vlessUuid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "serverEndpoint": "198.51.100.1",
  "serverPort": 8443,
  "realityPublicKey": "LS0tLS1CRUdJTiBQVUJMSUMgS0VZLS0tLS0K...",
  "realitySNI": "www.microsoft.com"
}
401Invalid or expired device token
{
  "success": false,
  "error": {
    "code": "UNAUTHORIZED",
    "message": "Invalid or expired device token"
  }
}

Response Fields

FieldTypeDescription
successbooleanWhether the connection was established
vlessUuidstringAssigned VLESS UUID for this session. Use this as the user ID in your VLESS client configuration.
serverEndpointstringServer IP address or hostname
serverPortintegerServer port (default 8443)
realityPublicKeystringREALITY public key for TLS camouflage. Used by the client to establish the REALITY handshake.
realitySNIstringServer Name Indication value for REALITY. The connection appears as HTTPS traffic to this domain.

REALITY Camouflage

REALITY is an advanced TLS camouflage technology. When a DPI system inspects the connection, it sees a valid TLS handshake to www.microsoft.com (or another configured SNI). The actual VPN traffic is indistinguishable from legitimate HTTPS. This makes VLESS+REALITY one of the most censorship-resistant protocols available.


Disconnect (Client)

Terminates an active VLESS connection and removes the user session from the server.

POST/vless/disconnect

Disconnect the current VLESS tunnel and clean up the session

Authentication:Bearer Token

Code Examples

curl -X POST https://198.51.100.1:8443/vless/disconnect \
  -H "Authorization: Bearer DEVICE_TOKEN"

Response

200VLESS session disconnected and cleaned up
{
  "success": true,
  "message": "Disconnected successfully"
}

Server Status (Internal)

Returns the current VLESS service status, including whether REALITY is enabled and the active user count. Used by OrbNET for monitoring.

GET/vless/status

Get VLESS server status including REALITY state and user count

Authentication:API Key

Internal Endpoint

This endpoint is called by OrbNET for server monitoring and orchestration. It is not intended for client applications. Access requires an internal API key.


Code Examples

curl -X GET https://198.51.100.1:8443/vless/status \
  -H "X-API-Key: INTERNAL_API_KEY"

Response

200VLESS server status
{
  "success": true,
  "enabled": true,
  "running": true,
  "publicKey": "LS0tLS1CRUdJTiBQVUJMSUMgS0VZLS0tLS0K...",
  "userCount": 37,
  "endpoint": "198.51.100.1:8443"
}

VLESS TCP Tunnel

Establishes the raw VLESS TCP tunnel for data transport. This endpoint handles the actual VLESS protocol data flow after a connection has been established via /vless/connect.

POST/vless/tunnel

VLESS TCP tunnel for data transport with optional bridge relay

Authentication:Bearer Token

Dual Authentication

This endpoint accepts both JWT bearer tokens (for client connections) and API keys (for bridge server-to-server relay). When a bridge server forwards traffic from its entry node to this exit server, it authenticates with an API key.


Code Examples

# Client connection (JWT auth)
curl -X POST https://198.51.100.1:8443/vless/tunnel \
  -H "Authorization: Bearer DEVICE_TOKEN" \
  -H "Content-Type: application/octet-stream" \
  --data-binary @vless_payload.bin

# Bridge relay (API key auth)
curl -X POST https://198.51.100.1:8443/vless/tunnel \
  -H "X-API-Key: BRIDGE_API_KEY" \
  -H "Content-Type: application/octet-stream" \
  --data-binary @relay_payload.bin

Add User (Internal)

Provisions a VLESS user on the server. Called by OrbNET during user setup. Returns the assigned VLESS UUID.

POST/vless/add-user

Provision a new VLESS user on the server (called by OrbNET)

Authentication:API Key

Internal Management Endpoint

This endpoint is called exclusively by OrbNET for user lifecycle management. Client applications should use /vless/connect instead.


Request Parameters

ParameterTypeRequiredDescription
userUuidstring RequiredThe unique user identifier from OrbNET.
emailstring RequiredThe user's email address for identification and logging.

Code Examples

curl -X POST https://198.51.100.1:8443/vless/add-user \
  -H "X-API-Key: INTERNAL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "userUuid": "usr_abc123",
    "email": "user@example.com"
  }'

Response

200VLESS user provisioned successfully
{
  "success": true,
  "vlessUuid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
}

Remove User (Internal)

Removes a VLESS user from the server and terminates any active sessions. Called by OrbNET during user cleanup.

POST/vless/remove-user

Remove a VLESS user from the server (called by OrbNET)

Authentication:API Key

Internal Management Endpoint

This endpoint is called exclusively by OrbNET. Client applications should use /vless/disconnect instead.


Request Parameters

ParameterTypeRequiredDescription
userUuidstring RequiredThe unique user identifier whose VLESS account should be removed.

Code Examples

curl -X POST https://198.51.100.1:8443/vless/remove-user \
  -H "X-API-Key: INTERNAL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "userUuid": "usr_abc123"
  }'

Response

200VLESS user removed successfully
{
  "success": true,
  "message": "User removed successfully"
}