New v5.5.1: balance-first checkout — add funds once, buy instantly. Read more
Getting started

Export formats

The five proxy line formats available in the dashboard and the API, which tools expect which, and how to convert between them.

On this page

Every proxy list in the dashboard — mobile, static ISP and generated residential endpoints — can be copied or downloaded as a .txt file in one of five formats. The same formats are available for residential endpoints through the format parameter of GET /residential/endpoints; for mobile and static proxies, the API returns JSON fields from which you build the lines. Multi-format exports shipped with v5.4.2 in September 2026.

The formats#

Format id Pattern Example
host_port_user_pass host:port:user:pass fr.mobile.gw.proxuno.com:10421:m_k3v9q2xa:Hq7Lr2Nw8Zt4Bc6D
user_pass_at_host_port user:pass@host:port m_k3v9q2xa:[email protected]:10421
user_pass_host_port user:pass:host:port m_k3v9q2xa:Hq7Lr2Nw8Zt4Bc6D:fr.mobile.gw.proxuno.com:10421
url scheme://user:pass@host:port http://m_k3v9q2xa:[email protected]:10421
host_port host:port fr.mobile.gw.proxuno.com:10421 (requires IP whitelist)

host_port_user_pass is the default and the format most proxy checkers, SEO tools and antidetect browsers import. The url format is what HTTP libraries expect (requests, httpx, undici, cURL's -x).

Protocol#

Each export is generated for one protocol:

  • HTTP — mobile: the proxy's HTTP port (10000–19999, ports.http in the API), residential 7000, static 8000. HTTPS targets work through CONNECT.
  • SOCKS5 — mobile: HTTP port + 10000 (ports.socks5), residential 7001, static 8001. In the url format the scheme becomes socks5://; most clients also accept socks5h:// to resolve DNS on the proxy.

From the API#

Mobile and static lists:

cURL
curl "https://proxuno.com/api/v1/proxies?type=mobile&status=active" -H "Authorization: Bearer $PROXUNO_API_KEY"

Each proxy object carries host, ports.http, ports.socks5, username and password — build any line format from those fields. Residential endpoints are generated directly in the format you ask for:

cURL
curl "https://proxuno.com/api/v1/residential/endpoints?country=fr&count=50&format=user_pass_at_host_port&protocol=socks5" \
  -H "Authorization: Bearer $PROXUNO_API_KEY"

See Residential endpoints API for every parameter.

Converting a list locally#

From host:port:user:pass to URLs:

cURL
awk -F: '{ printf "http://%s:%s@%s:%s\n", $3, $4, $1, $2 }' proxies.txt > proxies-url.txt

In Python:

Python
def to_url(line: str, scheme: str = "http") -> str:
    host, port, user, password = line.strip().split(":")
    return f"{scheme}://{user}:{password}@{host}:{port}"

with open("proxies.txt") as f:
    urls = [to_url(l) for l in f if l.strip()]

Notes#

  • Files are plain UTF-8 text, one proxy per line, \n line endings, no header.
  • Exports contain live credentials. Treat the file like a password and delete it from shared drives after import.
  • Static ISP lines use the IP address as host, so they keep working even if your resolver blocks gw.proxuno.com.

Something unclear, outdated or wrong on this page? Tell us — documentation issues are fixed in the next release at the latest.

Report an issue with this page