Configure Dedicated Ports
Assign dedicated TCP/UDP ports to an endpoint. By default, TCP and UDP endpoints share the platform's port pool — clients connect to tunnel-server:443 with SNI/ALPN to route. With dedicated ports, the endpoint is reachable directly at tunnel-server:<port>, no SNI required. Useful for databases, game servers, MUDs, or any TCP/UDP client that doesn't speak SNI.
This is a plan-gated feature — your plan must include the dedicated_ports entitlement, and you may have a per-plan max-count cap (-1 means unlimited). Some plans also require an extra verification gate (email verified, payment method on file, ID verified) before dedicated ports are usable.
Pass null for either field to clear that port assignment. If the requested port is already in use by another endpoint on that protocol you'll get a 409 — pick a different port. Ports are per protocol: another endpoint may hold the same number over the other protocol (for example TCP 5000 on one endpoint and UDP 5000 on another), and one endpoint may use the same number for both. The platform stores exactly the ports you request (it does not silently reassign).
Path parameters
Request body
1024–65535. Pass null to clear.1024–65535. Pass null to clear.Response (200 OK)
true on success.null if cleared.null if cleared.Errors
1024–65535.dedicated_ports entitlement, max-count limit reached, or verification gate not satisfied. Verification failures return JSON with error: "verification_required" + gate_type.