Connect to Graviix in a Few Lines of Code

Endpoint and authentication

Your dashboard issues a hostname, port, username, and password. Use them as an upstream proxy; no SDK or custom client is required. The default HTTP proxy port is shown below, and SOCKS5 is available on request for plans that support it.

The hostname and port shown in your dashboard are authoritative. If your account is provisioned on a different endpoint or port, use the values displayed there instead of the defaults above.

Targeting headers

Add request headers to influence which IP is selected. If a requested location is unavailable, the router falls back to another IP in the same country rather than failing the request.

Rotating and sticky sessions

Without a session header, each request can be routed through a different IP. This is the usual choice for broad collection jobs. When a workflow needs continuity — a login, a cart, or a multi-step form — send the same X-Graviix-Session value on each request to keep the same exit IP until the session expires.

• Rotating sessions are billed by bandwidth used.
• Sticky sessions hold an IP for a configurable period, subject to availability.
• Create a new session token to leave a sticky IP cleanly.

Code examples

cURL

curl -x http://proxy.graviix.com:8080 \
  -U "USERNAME:PASSWORD" \
  -H "X-Graviix-Country: US" \
  -H "X-Graviix-City: new-york" \
  https://httpbin.org/ip

Python (requests)

import requests

proxies = {
    "http": "http://USERNAME:PASSWORD@proxy.graviix.com:8080",
    "https": "http://USERNAME:PASSWORD@proxy.graviix.com:8080",
}
headers = {
    "X-Graviix-Country": "US",
    "X-Graviix-City": "new-york",
}
response = requests.get("https://httpbin.org/ip", proxies=proxies, headers=headers, timeout=30)
print(response.json())

Node.js (axios)

const axios = require("axios");

const response = await axios.get("https://httpbin.org/ip", {
  proxy: {
    host: "proxy.graviix.com",
    port: 8080,
    auth: { username: "USERNAME", password: "PASSWORD" },
  },
  headers: {
    "X-Graviix-Country": "US",
    "X-Graviix-City": "new-york",
  },
});

console.log(response.data);

PHP (cURL)

<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, "https://httpbin.org/ip");
curl_setopt($ch, CURLOPT_PROXY, "proxy.graviix.com:8080");
curl_setopt($ch, CURLOPT_PROXYUSERPWD, "USERNAME:PASSWORD");
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    "X-Graviix-Country: US",
    "X-Graviix-City: new-york",
]);
echo curl_exec($ch);
curl_close($ch);

SOCKS5 support

SOCKS5 routes TCP traffic through the proxy without rewriting HTTP headers, which is useful for clients that do not speak HTTP proxies. Use socks5h://USERNAME:PASSWORD@proxy.graviix.com:1080 so DNS is resolved at the exit point. SOCKS5 availability depends on your plan; check the dashboard or ask support before building a workflow that depends on it.

curl --socks5-hostname proxy.graviix.com:1080 \
  -U "USERNAME:PASSWORD" \
  https://httpbin.org/ip

Common status codes

Questions we get about setup