Scrapling Proxy Setup: German Mobile IP Across Every Fetcher

Direct Answer

To use a mobile proxy with Scrapling, pass your endpoint to the proxy argument on any fetcher — Fetcher, StealthyFetcher or DynamicFetcher — as a http://user:pass@host:port string. Scrapling then routes both HTTP and HTTPS through your real German mobile IP, pairing its browser-shaped fetch with an everyday-consumer connection. Add your host, port, username and password from your account.

One Proxy Argument, Three Fetchers

Scrapling is an adaptive Python scraping library that ships three fetchers for three levels of difficulty, all sharing one API. Fetcher is a fast HTTP client built on curl_cffi, so it already reproduces a browser-consistent TLS handshake. StealthyFetcher and DynamicFetcher drive a real browser engine (Playwright) for pages that only render with JavaScript. The gotcha people hit is assuming each fetcher wires proxies differently — they don't. The same proxy argument works across all three, so once you have it right you can swap fetchers freely.

What that argument does not do is change where the request comes from. A browser-shaped fetch is only half of a coherent request; the other half is the IP it arrives on. When the fetch looks like a browser but the connection is a flagged server range, the two stories disagree — and it is the disagreement that stands out. For how that transport fingerprint is read, see TLS fingerprinting with JA3 and JA4. The aim is consistency, not concealment: look like the ordinary browser you are, from an IP that fits.

Install

Scrapling installs as one package. For the browser fetchers you also fetch the browser engine once:

pip install scrapling
scrapling install

The import style is the same regardless of which fetcher you use:

from scrapling.fetchers import Fetcher, StealthyFetcher, DynamicFetcher

Before You Start

You will need four values from your GermanProxy.io account:

Host and port of your endpoint
Username and password

The examples use PROXY_HOST, PORT, USER and PASS as placeholders — replace them with your own. GermanProxy.io supports HTTP, SOCKS5 and OpenVPN, so you can pick whichever your fetcher prefers.

Step 1 — `Fetcher` (fast HTTP through the proxy)

Fetcher is the quickest path: an HTTP request over curl_cffi with a browser-consistent handshake built in. Pass the endpoint as a proxy string:

from scrapling.fetchers import Fetcher

PROXY = "http://USER:PASS@PROXY_HOST:PORT"

page = Fetcher.get(
    "https://www.example.de",
    proxy=PROXY,
    timeout=30,
)
print(page.status)
print(page.css_first("title::text"))

Because Fetcher sits on libcurl, you can also hand it a socks5://USER:PASS@PROXY_HOST:PORT string when you prefer SOCKS5. For the trade-offs, see SOCKS5 vs HTTP proxy.

Step 2 — `StealthyFetcher` and `DynamicFetcher` (browser engine)

When a target only renders with JavaScript, switch to a browser fetcher. The proxy argument is identical — a string, or a dictionary with server, username and password:

from scrapling.fetchers import StealthyFetcher

# String form
page = StealthyFetcher.fetch(
    "https://www.example.de",
    proxy="http://USER:PASS@PROXY_HOST:PORT",
)

# Dictionary form (same endpoint, split out)
page = StealthyFetcher.fetch(
    "https://www.example.de",
    proxy={
        "server": "http://PROXY_HOST:PORT",
        "username": "USER",
        "password": "PASS",
    },
)
print(page.status)

DynamicFetcher takes the same proxy argument if you want full Playwright control. Because these fetchers drive a browser engine, use the HTTP endpoint here rather than SOCKS5.

Verify the IP First

Before scaling up, request an IP-echo endpoint through the same proxy and confirm the German mobile IP your target actually sees:

from scrapling.fetchers import Fetcher

page = Fetcher.get("https://api.ipify.org?format=json",
                   proxy="http://USER:PASS@PROXY_HOST:PORT")
print(page.body)

If it returns your own address, re-check the proxy string. You can also open the how to verify your setup guide to compare.

Sticky Sessions vs. Rotation

With a single dedicated endpoint you control the IP at the proxy, not with a pool:

Sticky session: keep the same German mobile IP across a multi-request flow.
Rotation on demand: request a fresh IP at the proxy when you want to spread load.

Scrapling ships a ProxyRotator, but with one dedicated endpoint you don't need it — rotate at the proxy instead. See sticky sessions and IP rotation explained.

Why a Real German Mobile IP

A fetcher settles how the request looks; the IP settles where it comes from. A real German 5G mobile IP is a normal consumer address on a real German mobile network, shared across many everyday users through CGNAT, so its reputation reflects ordinary phone traffic rather than a server range. Paired with Scrapling's browser-shaped fetch, both stories agree — this is the whole-request view that how websites detect proxies describes, and why a clean IP reputation matters as much as the fetcher. For the spectrum of options, see mobile vs residential vs datacenter proxies.

Scrape Responsibly

A browser-shaped fetcher on a clean mobile IP improves reliability for legitimate data collection — it is not a way around access controls or a site's rules. Keep the pipeline defensible:

Respect robots.txt and each site's terms of service.
Send requests at a human-reasonable rate — add delays; do not hammer servers.
Collect only public data you need, and handle any personal data in line with the GDPR.
Keep your User-Agent honest and aligned with the fetcher you use.

For German and EU targets this is our positioning: public data only, polite rates, no storing of personal data. See EU rules on scraping.

FAQ

Which Scrapling fetcher should I put the proxy on?

All three take the same proxy argument. Use Fetcher for a fast curl_cffi HTTP request, StealthyFetcher when a page needs a real browser engine, and DynamicFetcher for full Playwright control. The proxy string format is identical across them, so switching fetcher is a one-line change.

What proxy string format does Scrapling expect?

A single URL string, http://USER:PASS@PROXY_HOST:PORT, passed to the proxy argument. The browser fetchers also accept a dictionary with server, username and password keys. Both route HTTP and HTTPS through the same German mobile endpoint.

Does Scrapling support SOCKS5 proxies?

The plain Fetcher is built on curl_cffi and libcurl, so it accepts a socks5:// URL as well as http://. The browser-based fetchers speak the Playwright proxy format, which is HTTP-oriented; use the HTTP endpoint there. For most Scrapling work an HTTP endpoint is the simplest choice.

Do I still need a mobile IP if Scrapling already matches a fingerprint?

Yes. Scrapling's fetchers shape the request and, in the browser fetchers, the client fingerprint — but your IP is a separate signal. A browser-shaped fetch from a flagged datacenter range is still inconsistent. A real German mobile IP gives the network layer the everyday-consumer profile the fetch already claims.

Can I rotate the IP between Scrapling runs?

With one dedicated German endpoint you keep a sticky session for a multi-step flow, then rotate on demand at the proxy when you want a fresh IP. You do not need Scrapling's ProxyRotator or a pool of endpoints for that — the rotation happens at the proxy, not in your fetcher list.

Why does a German mobile IP help with German targets specifically?

German e-commerce and price data is often served in the language, prices and availability that a domestic visitor sees. A real German mobile IP makes your Scrapling fetch look like an ordinary German phone on a German network, so you collect the same public view a local user would.

Related guides

CTA

Give your Scrapling fetchers an IP that fits. Start with a German mobile proxy — HTTP/SOCKS5/OpenVPN, sticky sessions, on-demand rotation, fair-use 20 GB/day, from a transparent EU provider.

Get a German mobile proxy: Real 4G/5G IPs from Germany, fair-use 20 GB/day — browse German mobile proxy plans or start with a dedicated 5G proxy.