LogoLogo
Nimble HomeLoginCreate an Account
  • Home
  • Quick Start Tutorials
    • Tutorial Library
      • Track SEO and SEM Ranking
      • Reddit as a Guerilla Marketing Strategy
  • Nimble Platform
    • Nimble Platform Overview
    • Online Pipelines
      • Supermarkets
        • ASDA
        • Tesco Groceries
        • Sainsbury’s
        • Morrisons
      • eCommerce
      • Restaurants
        • Yelp
        • Tabelog
        • Uber Eats Japan
        • Demaecan
        • Uber Eats US
      • Real Estate
        • Zillow
  • Nimble SDK
    • SDK Overview
    • Web API
      • Web API Overview
      • API Product Specs
      • Nimble Web API Quick Start Guide
        • Introduction
        • Nimble APIs Authentication
        • Real-time URL request
        • Delivery methods
        • Batch processing
        • Response codes
        • FAQs
      • Nimble Web API Functions
        • Realtime, Async & Batch Request
        • Geo Location Targeting
        • Javascript Rendering
        • Page Interaction
          • Wait (delay)
          • Wait for Selector
          • Wait and Click
          • Wait and Type
          • Scroll
          • Scroll to
          • Infinite Scrolling
          • Capturing Screenshots
          • Collecting Cookies
          • Executing HTTP Requests
          • Operation Reference
        • Network Capture
          • Filter by URL Matching
          • Filter By Resource Type
            • Real World Demo: Capturing Ajax Requests
          • Wait for Requests
          • Capturing XHR without Rendering
          • Operation Reference
        • Data Parsing
          • Parsing Templates
          • Merge Dynamic Parser
        • Custom Headers & Cookies
        • General Params
      • Vertical Endpoints
        • SERP API
          • Real-time search request
          • Getting local data
          • Browsing SERP pagination
          • Delivery methods
          • Batch Processing
          • Endpoints and Response Codes
        • Maps API
          • Searching for places
          • Getting information about a place
          • Collecting reviews
          • Delivery methods
          • Batch processing
          • Endpoints and Response Codes
    • Web Retrieval API
      • Web Retrieval API Overview
    • Proxy API
      • Nimble IP Overview
      • Nimble IP Quick Start Guide
        • Send a request
        • Nimble IP Autentication
        • Geotargeting and session control
        • Response codes
        • FAQs
      • Nimble IP Functions
        • Country/state/city geotargeting
        • Controlling IP rotation
        • Geo-sessions: longer, stickier, more accurate sessions
        • Using IPv6 Proxies
        • Response Codes
      • Integration Guides
        • Incogniton
        • Kameleo
        • VMLogin
        • AdsPower
        • FoxyProxy
        • Android
        • Multilogin
        • iOS
        • SwitchyOmega
        • Windows
        • macOS
        • Proxifier
        • MuLogin
        • Puppeteer
        • Selenium
        • Scrapy
    • Client Libraries
      • Installation
      • Quick Start
    • LangChain Integration
  • Technologies
    • Browserless Drivers
      • API Driver-Based Pricing
    • IP Optimization Models
    • AI Parsing Skills
  • Management Tools
    • Nimble Dashboard
      • Exploring the User Dashboard
      • Managing Pipelines
      • Reporting and Analytics
      • Account Settings
      • Experimenting with the Playground
      • Billing and history
    • Nimble Admin API
      • Admin API basics
      • Admin API reference
  • General
    • Onboarding Guide
      • Getting started with Nimble's User Dashboard
      • Nimble IP Basics
      • Nimble API Basics
      • Helpful Resources
    • FAQs
      • Account Settings and Security
      • Billing and Pricing
      • Tools and Integrations
      • Nimble API
      • Nimble IP
    • Deprecated APIs
      • E-commerce API
        • E-commerce API Authentication
        • Real-time product request
        • Real-time product search request
        • Delivery methods
        • Batch Processing
        • Endpoints and Response Codes
      • Unlocker Proxy Overview
        • Unlocker Proxy Quick Start Guide
          • Real-time request
          • FAQs
        • Unlocker Proxy FAQ
Powered by GitBook
On this page
  • Configuring proxy settings
  • Entering credentials
  • Controlling your connection
  • Allow-listing your IP instead of using credentials
  1. Nimble SDK
  2. Proxy API
  3. Integration Guides

Windows

PreviousSwitchyOmegaNextmacOS

Last updated 2 months ago

Configuring Windows to work with Nimble IP allows any running application to use the proxy connection for its communication over the internet.

In the latest versions of Windows OS (10 and up), the server and port are set by the OS, whereas the credentials (username and password) must be set by each application individually.

Configuring proxy settings

  1. To get started, open “Proxy settings” on Windows - click the Windows key and search for “proxy settings”.

  • You can also find Proxy settings under “Network & Internet” settings.

2. There are two ways to set up a proxy; by script or manually. In this guide, we’ll set up the proxy manually - click on “Set up” to add a proxy server and port.

3. To use the proxy, switch “Use a proxy server” to ON, then add ip.nimbleway.com as your “Proxy IP server”, enter port 7000, and then click “Save” to enable your setup.

Entering credentials

As each application must manage its own credentials in Windows 10 and later, the way to set the username and password depends on the application you’re using. For example, to set your credentials in Chrome:

  1. Open Chrome.

  2. Enter the URL for the page you wish to visit.

  3. Chrome will prompt you for Nimble’s Backconnect proxy gateway credentials:

4. Enter your Nimble proxy username and password (provided by your account manager when your account was opened).

5. Click Sign in and your page will load through Nimble IP.

Controlling your connection

By modifying your connection string, you can control your targeted location. See Nimble’s Backconnect Gateway guide for all username configuration options.

Allow-listing your IP instead of using credentials

In some cases, it’s easier to allow-list your IP in your Pipeline settings instead of using credentials. This allows you to connect to Nimble IP, with all session controls managed by your Pipeline’s default settings.

If you'd like to learn more about using Allow-lists and managing pipelines, see our Nimble IP documentation.