Skip to main content

TUIC API reference and data availability

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

API documentation is temporarily excluded from search. The protocol dataset has not yet met the 10-endpoint, 3-source and 7-of-14-day publication gate. The route remains available to users and returns no invented rows.

Request example

curl -H 'Accept: application/json' \
  'https://publicvpnlist.com/api/v1/servers?protocol=tuic&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 TUIC record means

TUIC uses UDP/QUIC proxy tunnels. A usable public configuration requires UUID, password, TLS name and UDP reachability. PublicVPNList does not publish rows inferred from an open port or incomplete relay metadata.

FieldMeaning
hostname, ip, portPublic connection endpoint metadata.
transport, transport_securityTransport settings required by the client.
exit_ipPublic IP observed only after the checker routed traffic through the tunnel.
handshake_ms, https_first_byte_msChecker-region measurements; they are not a speed guarantee for every user.
config_download_urlCurrent 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: 20260908T101804Z-c62555ecd975. API JSON routes are excluded from search indexing; this documentation page is the canonical indexable explanation.