Proxy Basics - FloppyData Client API

Learn how to use Floppydata proxies to route your requests through residential, mobile, or datacenter IPs with precise control.

How it works

When you connect through Floppydata, you describe how your request should behave — and Floppydata handles routing automatically.

Traditional approach

Manual proxy selection
Rotation management
Proxy list maintenance

Floppydata approach

Describe the request
Automatic routing
Infrastructure abstraction

You don’t choose proxies manually. You describe how your request should behave – Floppydata handles the routing automatically.

The gateway

Your application always connects to a single proxy endpoint:

geo.g-w.info

You don’t switch hosts for different countries or proxy types. All routing is controlled by Smart Parameters in the username.

Available ports

Port	Protocol	Use case
`10080`	HTTP	Default, works with most tools
`10443`	HTTPS	Secure HTTP connection
`10800`	SOCKS5	Advanced use, automation tools

Not sure which port? Start with 10080 (HTTP)

Connection format

http://USERNAME:PASSWORD@geo.g-w.info:PORT

Example:

http://user123-type-residential-country-US:yourpassword@geo.g-w.info:10080

The magic happens in the username — Smart Parameters control where and how your request is routed.

What the target website sees

Without proxy
With Floppydata

When you send requests directly, the target website sees your real IP address.

Your App → Target Website
(sees your real IP: 203.0.113.45)

When you send requests through Floppydata, the target sees the proxy exit IP instead. Your real IP stays hidden.

Your App → Floppydata → Target Website
(sees proxy IP: 123.45.67.89 from US)

This is what makes geo-targeting, rotation, and session control possible.

Proxy types

Smart Parameters support three rotating proxy types:

residential
mobile
datacenter

Static IPs are a separate product. For static IPs, use the credentials returned by the Static IP List endpoint instead of adding a Smart Parameter type.

Residential

Real user IPs with high trust levelCharacteristics:

🔹 Rotating IPs from shared pool
🔹 High trust level
🔹 Medium speed
🔹 Billed per GB

Best for: Web scraping, SEO tracking, geo-targeting, price monitoringPricing: $5/GB

Mobile (4G/5G)

Mobile carrier IPs with highest trust levelCharacteristics:

🔹 Rotating IPs from mobile networks
🔹 Very high trust level
🔹 Medium speed
🔹 Billed per GB

Best for: Social media automation, high-risk targets, account creation, sneaker botsPricing: $15/GB

Datacenter

Fast and cost-efficient IPs for scaleCharacteristics:

🔹 Rotating IPs from datacenters
🔹 Low trust level
🔹 Fast speed
🔹 Billed per GB

Best for: High-volume scraping, simple sites, speed-critical tasksPricing: $0,6/GB

Static IPs

ISP Static

Fixed residential IP for account stabilityCharacteristics:

🔹 Fixed IP assigned to you
🔹 High trust level
🔹 Fast speed
🔹 Billed per IP/month

Best for: Account management, long sessions, multi-accounting, e-commerce accountsPricing: $5/IP/month

Datacenter Static

Fixed datacenter IP for infrastructureCharacteristics:

🔹 Fixed IP assigned to you
🔹 Medium trust level
🔹 Fast speed
🔹 Billed per IP/month

Best for: Automation tools, API access, IP whitelistingPricing: $1/IP/month

How to choose proxy type

Use case	Recommended proxy	Why
Social media accounts	Mobile or Static ISP	High trust + stable identity
Ad accounts (Meta, Google)	Static ISP or Mobile	Geo-consistency required
E-commerce (Amazon, eBay)	Static ISP	Fixed IP avoids account linking
Payment platforms	Static ISP	IP changes trigger security checks
Account creation	Mobile	Mobile IPs have highest trust
SEO & SERP tracking	Residential	Accurate geo-targeting
Price monitoring	Residential	Access localized content
Web scraping (protected)	Residential	Higher success rate
Web scraping (high volume)	Datacenter	Faster and cheaper at scale
Automation tools	Datacenter or Static DC	Speed and performance
Sneaker/ticketing bots	Mobile or Residential	Avoid detection systems

General rule:

Use Rotating proxies when you need scale and request distribution
Use Static proxies when you need a stable identity

Smart Parameters

Smart Parameters define how your requests are routed. They’re added to the username.

Format

USERNAME-parameter1-value1-parameter2-value2

Example

user123-type-residential-country-US-city-New_York-session-abc123

This means:

type-residential — use residential proxies
country-US — route through United States
city-New_York — narrow to New York
session-abc123 — keep same IP (sticky session)

Available parameters

type

string

Rotating proxy type to useValues:

residential — Residential
mobile — Mobile (4G/5G)
datacenter — Datacenter

Example: user123-type-mobile-country-US

country

string

Exit country using ISO codeExamples:

country-US — United States
country-GB — United Kingdom
country-DE — Germany

Example: user123-type-residential-country-FR

city

string

Exit city (use underscores for spaces)Examples:

city-New_York
city-Los_Angeles
city-London

Note: Falls back to country-level if city unavailableExample: user123-type-residential-country-US-city-Chicago

state

string

US state targeting (full name or abbreviation)Examples:

state-California or state-CA
state-North_Carolina or state-NC

Works with: Residential and Mobile proxies onlyExample: user123-type-residential-country-US-state-California

asn

number

Target specific ISP network by Autonomous System NumberExample: user123-type-residential-country-US-asn-7018Works with: Residential and Mobile proxies onlyUse case: Better compatibility with specific ISP networks

session

string

Sticky session ID (keeps same IP)Behavior:

Same session ID → same IP
Different session ID → different IP
Combine with rotation-0 for a stable session IP

Lifetime: Up to 10 minutes of inactivityExample: user123-type-residential-country-US-session-login01

rotation

number

Rotation interval in minutesValues:

-1 — new IP every request
0 — keep the same IP within a session
1 to 60 — rotate after this many minutes

Example: user123-type-residential-country-US-rotation--1

Sessions and rotation

Per-request rotation

Set rotation to -1 when you want a new IP for every request:

proxy_username = "user123-type-residential-country-US-rotation--1"

When you build this through the API, pass rotation=-1. In the generated username, the negative value appears as rotation--1.

Sticky sessions

To keep the same IP across multiple requests, use a session:

# Same session = same IP
proxy_username = "user123-type-residential-country-US-session-checkout01"

What happens:

All requests with the same session ID use the same IP
Changing the session ID assigns a new IP
rotation-0 keeps the same IP within the session

Session lifetime

Sessions stay active for up to 10 minutes of inactivity. Each request resets the timer.

00 → Request (IP A)
05 → Request (IP A) — session alive
14 → Request (IP A) — session alive
25 → Request (IP B) — session expired after 10min inactivity

Interval rotation

Use a value from 1 to 60 to rotate after that many minutes:

proxy_username = "user123-type-residential-country-US-session-crawl01-rotation-15"

Changing IP manually

To get a new IP before session expires, change the session value:

# Original session
"user123-type-residential-country-US-session-s01"  # → IP A
 
# New session → new IP
"user123-type-residential-country-US-session-s02"  # → IP B

There is no reset endpoint — changing the session string is how you rotate

Multiple sessions

Run multiple sessions simultaneously:

"user123-type-residential-country-US-session-user1"  # → IP A
"user123-type-residential-country-US-session-user2"  # → IP B
"user123-type-residential-country-US-session-user3"  # → IP C

Each session gets its own IP for parallel workflows.

When to use rotation vs sessions

Use Rotation
Use Sessions

Use rotation when:

Scraping many pages
Collecting large datasets
Avoiding rate limits
Distributing requests
No login required

Example:

# Scraping 1000 product pages
proxy_username = "user123-type-residential-country-US-rotation--1"  # New IP each request

Use sessions when:

Logging into accounts
Maintaining cookies
Checkout flows
Multi-step interactions
Account-based automation

Example:

# Login flow with multiple steps
proxy_username = "user123-type-residential-country-US-session-login01"  # Same IP

Geo targeting

Control where your requests originate from.

Country-level targeting

proxy_username = "user123-type-residential-country-US"  # United States
proxy_username = "user123-type-residential-country-GB"  # United Kingdom
proxy_username = "user123-type-residential-country-DE"  # Germany

City-level targeting

proxy_username = "user123-type-residential-country-US-city-New_York"
proxy_username = "user123-type-residential-country-US-city-Los_Angeles"
proxy_username = "user123-type-residential-country-GB-city-London"

Use underscores instead of spaces in city names

State-level targeting (US only)

proxy_username = "user123-type-residential-country-US-state-CA"  # California
proxy_username = "user123-type-residential-country-US-state-New_York"

Available locations

Check available countries and cities via API:

curl -H "X-Api-Key: YOUR_KEY" \
  https://api.floppydata.net/v1/rotating/locations

Fallback behavior

If a specific city is unavailable, Floppydata automatically falls back to country-level routing.

Parameter combinations

Common patterns

"user123-type-residential-country-US"

Complete examples

Python

import requests
 
PROXY_USER = "user123"
PROXY_PASS = "your_password"
 
# Residential, US, sticky session
proxy_username = f"{PROXY_USER}-type-residential-country-US-session-checkout01"
proxy_url = f"http://{proxy_username}:{PROXY_PASS}@geo.g-w.info:10080"
 
proxies = {
    'http': proxy_url,
    'https': proxy_url
}
 
response = requests.get('https://example.com', proxies=proxies)
print(response.text)

Node.js

const axios = require('axios');
 
const PROXY_USER = 'user123';
const PROXY_PASS = 'your_password';
 
// Mobile, US, New York
const proxyUsername = `${PROXY_USER}-type-mobile-country-US-city-New_York`;
 
const proxy = {
    host: 'geo.g-w.info',
    port: 10080,
    auth: {
        username: proxyUsername,
        password: PROXY_PASS
    }
};
 
axios.get('https://example.com', { proxy })
    .then(res => console.log(res.data));

Common questions

Why is my IP changing every request?

Per-request rotation is enabled with rotation--1. To keep the same IP, add a session parameter and rotation-0:

-session-YOUR_ID-rotation-0

Why is my IP not changing?

You’re using a session. To rotate:

Remove the session parameter
Change the session value
Or use rotation--1

How long do sessions last?

Sessions last up to 10 minutes of inactivity. Each request resets the timer.To keep a session alive longer, send periodic requests.

Can I use multiple sessions?

Yes! Each unique session ID gets its own IP. Run as many parallel sessions as needed.

​How it works

Traditional approach

Floppydata approach

​The gateway

​Available ports

​Connection format

​What the target website sees

​Proxy types

​Static IPs

​How to choose proxy type

​Smart Parameters

​Format

​Example

​Available parameters

​Sessions and rotation

​Per-request rotation

​Sticky sessions

​Session lifetime

​Interval rotation

​Changing IP manually

​Multiple sessions

​When to use rotation vs sessions

​Geo targeting

​Country-level targeting

​City-level targeting

​State-level targeting (US only)

​Available locations

​Fallback behavior

​Parameter combinations

​Common patterns

​Complete examples

​Python

​Node.js

​Common questions

How it works

The gateway

Available ports

Connection format

What the target website sees

Proxy types

Static IPs

How to choose proxy type

Smart Parameters

Format

Example

Available parameters

Sessions and rotation

Per-request rotation

Sticky sessions

Session lifetime

Interval rotation

Changing IP manually

Multiple sessions

When to use rotation vs sessions

Geo targeting

Country-level targeting

City-level targeting

State-level targeting (US only)

Available locations

Fallback behavior

Parameter combinations

Common patterns

Complete examples

Python

Node.js

Common questions