Capabilities
Public proxy capability matrix.
What NinjaProxy actually supports today — proxy types, sticky-session support, country targeting, and the exact routing controls our gateway accepts. Sourced from the live product, not marketing copy.
Last reviewed: 2026-06-20. See /metrics for measurement methodology.
Proxy types
What each product actually does.
Each row reflects the current product behavior. “Account-specific” means exact country list is shown in the portal for your active plan.
| Product | Network | Rotation | Sticky session | Country targeting | Protocols | Pricing |
|---|---|---|---|---|---|---|
| Shared Proxies | Datacenter | Assigned (static) | N/A (assigned) | Account-specific | HTTP + SOCKS5 | Subscription |
| Private Proxies | Datacenter | Assigned (static) | N/A (assigned) | Account-specific | HTTP + SOCKS5 | Subscription |
| Premium Proxies | Datacenter (premium peering) | Assigned (static) | N/A (assigned) | Account-specific | HTTP + SOCKS5 | Subscription |
| IPv6 Proxies | Datacenter IPv6 | Assigned (static) | N/A (assigned) | Account-specific | HTTP + SOCKS5 | Subscription |
| ISP / Residential Proxies | Real ISP-assigned IPs | Assigned (static) | N/A (assigned) | Account-specific | HTTP + SOCKS5 | Subscription |
| 4G/5G Mobile Proxies | Real mobile carrier IPs | Rotates ~15 min | No | USA + UK only | HTTP + SOCKS5 | Subscription |
| Pay-per-GB (rotating gateway) | Datacenter + Residential via gateway | Per-request (rotating gateway) | Yes | Yes | HTTP + SOCKS5 | Pay-per-GB |
Sticky sessions
Sticky-session support, in plain terms.
Rotating gateway endpoints accept structured username controls for sticky behavior. Assigned products (datacenter, ISP, residential) are static by design — the exit IP only changes when you swap the assignment in the portal.
- Sticky sessions are enabled by appending
--session-SESSION_IDto your username on a rotating gateway endpoint. - Default sticky TTL is 10 minutes; maximum configurable duration is 60 minutes via
--duration-SECONDS. - Header equivalents (
X-Session-ID,X-Session-Duration) are available on HTTP for clients that cannot embed controls in the username.
Full reference: /docs/rotating.
Country targeting
Geo coverage by product.
The routing layer supports country, region, city, and ISP/ASN targeting. The exact list of exit countries available on your plan is account-specific, so we surface it in the portal instead of quoting a public country count we cannot verify per-customer.
- Rotating gateway: country targeting via
--geo-country-CC(ISO 3166-1 alpha-2). Region and city targeting available via HTTP headers. - Mobile 4G/5G: USA and UK carrier networks only — other geographies require pre-sales scoping.
- Assigned (static) products: country and city are tied to the specific IP assigned to your account in the portal.
Need a specific country before buying? Contact pre-sales.
Session controls
Username and header reference.
These are the routing controls our rotating gateway accepts today. Append them to the username on a portal-assigned rotating endpoint, or pass equivalent HTTP headers.
Structured username controls
Append after the base username, separated by --.
| Control | Purpose | Example |
|---|---|---|
| --session-SESSION_ID | Keep one sticky route across requests | --session-checkout-flow-42 |
| --duration-SECONDS | Expire that sticky route after a fixed number of seconds | --duration-90 |
| --provider-dc | --provider-res | Force datacenter or residential routing | --provider-res |
| --geo-country-CC | Limit route to one country (2-letter ISO code) | --geo-country-us |
HTTP targeting headers
For clients that prefer headers over username controls.
| Header | Description |
|---|---|
| X-Target-Geo | Target country or region code (e.g. US, GB, DE, US-NY) |
| X-Target-City | Target city name (requires X-Target-Geo) |
| X-Target-ISP | Target ISP name (requires X-Target-Geo) |
| X-Target-ASN | Target ASN (requires X-Target-Geo) |
| X-Session-ID | Sticky session identifier (alternative to username suffix) |
| X-Session-Duration | Session duration in seconds before IP rotation (matches --duration-SECONDS) |
| X-Provider-Type | Preferred provider type: datacenter, residential, or mobile |
Example
A rotating gateway request with a sticky residential US session for 90 seconds:
curl -x "http://USERNAME--session-checkout-flow-42--duration-90--provider-res--geo-country-us:API_KEY@<ROTATING_HTTP_ENDPOINT>" \
"https://ip.ninjasproxy.com/"Replace placeholders with values from your account. Full guide: /docs/rotating.
Disclosure policy
What we will and will not claim publicly.
- We do not publish unaudited pool-size figures (e.g. "millions of IPs"). Exact pool composition and exit-country availability for your account are visible in the customer portal.
- Country targeting is supported architecturally on the rotating gateway. Available exit countries depend on upstream provider inventory under your active plan. Pre-sales can confirm specific countries on request.
- Mobile 4G/5G proxies are limited to USA and UK carrier networks today; other geographies require pre-sales scoping.
- Assigned (static) proxy products do not rotate — the IP changes only when you swap the assignment in the portal.
See /metrics for performance methodology and disclosure scope.