Skip to main content

​
Authentication Methods

Nimble supports two authentication methods for accessing the residential proxy network:

Username & Password

Include credentials in every request

IP Allowlist

Authenticate by trusted IP addresses

​
Username & Password Authentication

The most common method - include your account and pipeline credentials in the proxy connection string.

​
Connection Format

http://account-{accountName}-pipeline-{pipelineName}:{pipelinePassword}@ip.nimbleway.com:7000

​
Code Examples

curl -x http://account-accountName-pipeline-pipelineName:[email protected]:7000 \
  https://ipinfo.io
Replace accountName, pipelineName, and pipelinePassword with your actual credentials from the Nimble dashboard.

​
IP Allowlist Authentication

Authenticate requests based on trusted IP addresses without including credentials in each request.

​
How It Works

  1. Add your IP addresses to the pipeline’s allowlist in the Nimble dashboard
  2. Configure a custom port (between 9000-10000) for the pipeline
  3. Send requests from allowlisted IPs without username/password

​
Benefits

  • Simplified requests: No credentials in connection string
  • Enhanced security: Only specific IPs can access your pipeline
  • Cleaner code: Remove authentication logic from application code

​
Configuration

Configure IP allowlists through:
  • Nimble dashboard under pipeline settings
  • Admin API /account/pipelines endpoint

​
Example Request

cURL
curl -x http://ip.nimbleway.com:9000 https://ipinfo.io
Security Consideration: Avoid using shared IP addresses (like AWS shared IPs) in your allowlist. Other parties on the same shared IP could potentially use your account.

​
Choosing an Authentication Method

  • Running requests from dynamic IP addresses
  • Quick setup and testing
  • Multiple team members with different credentials
  • Cloud environments with rotating IPs
  • Fixed server infrastructure
  • Enhanced security requirements
  • High-volume automated systems
  • Simplified application code

​
Authentication Errors

Response CodeIssueSolution
407Proxy Authentication RequiredVerify account name, pipeline name, and password are correct
401UnauthorizedCheck that your IP is in the allowlist (if using IP authentication)
403ForbiddenPipeline may be disabled or you may have reached quota limits

Response Codes Reference

View complete list of response codes and troubleshooting steps

​
Next Steps

Geotargeting

Target specific countries, states, or cities

Session Control

Control IP rotation behavior