VLESS API reference and data availability

Use the PublicVPNList API to read VLESS endpoint metadata without scraping the HTML catalog. The current compact snapshot contains 40 fresh records from 7 independent sources for this protocol.

Live VLESS catalog VLESS guide OpenAPI JSON Verification method

Request example

curl -H 'Accept: application/json' \
  'https://publicvpnlist.com/api/v1/servers?protocol=vless&status=online&sort=last_checked&order=desc&per_page=50'

The response is paginated. Keep the returned id for details at /api/v1/servers/{id}, cache the ETag, and treat last_checked_at as technical evidence rather than a privacy guarantee.

What each VLESS record means

VLESS uses TCP, WebSocket or gRPC proxy tunnels with TLS or REALITY. A usable public configuration requires complete UUID and transport parameters. PublicVPNList does not publish rows inferred from an open port or incomplete relay metadata.

Field	Meaning
`hostname`, `ip`, `port`	Public connection endpoint metadata.
`transport`, `transport_security`	Transport settings required by the client.
`exit_ip`	Public IP observed only after the checker routed traffic through the tunnel.
`handshake_ms`, `https_first_byte_ms`	Checker-region measurements; they are not a speed guarantee for every user.
`config_download_url`	Current downloadable configuration for a still-fresh verified row.

Freshness, safety and caching

Only checks no older than 72 hours can enter the protocol snapshot. Every row requires a real client tunnel, a successful HTTPS request and a public exit IP different from the checker’s direct address. Unknown third-party endpoints can still log or alter traffic; use end-to-end encryption and avoid sensitive accounts.

Snapshot version: 20260908T092803Z-08ecdc3f9f0e. API JSON routes are excluded from search indexing; this documentation page is the canonical indexable explanation.