Skip to main content

​
Prerequisites

Before you begin, make sure you have:
  • A Nimble account with residential proxy access
  • Your account name and pipeline credentials
Don’t have an account yet? Contact our sales team to get started.

​
Basic Request Format

The Nimble BackConnect Gateway uses a standard proxy format: 
http://account-{accountName}-pipeline-{pipelineName}:{pipelinePassword}@ip.nimbleway.com:7000

​
Required Parameters

ParameterDescription
accountNameYour company gateway name
pipelineNamePipeline to use (default: “residential”)
pipelinePasswordYour pipeline authentication credential

​
Send Your First Request

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

​
Example Response

A successful request to ipinfo.io returns your current proxy IP details: 
{
  "ip": "203.0.113.45",
  "city": "Los Angeles",
  "region": "California",
  "country": "US",
  "loc": "34.0522,-118.2437",
  "org": "AS12345 Example ISP",
  "timezone": "America/Los_Angeles"
}

​
Quick Examples

​
Target a Specific Country

Add country targeting to your proxy connection: 
curl -x http://account-accountName-pipeline-pipelineName-country-US:[email protected]:7000 \
  https://ipinfo.io

​
Use a Sticky Session

Maintain the same IP across multiple requests: 
curl -x http://account-accountName-pipeline-pipelineName-session-mysession123:[email protected]:7000 \
  https://ipinfo.io

​
Common Response Codes

CodeMeaning
200Success
407Authentication failed - check credentials
525No suitable IP found for request parameters

View All Response Codes

See the complete list of response codes and their meanings

​
Next Steps

Authentication Methods

Learn about username/password and IP allowlist authentication

Geotargeting

Target specific countries, states, or cities

Session Control

Control IP rotation and sticky sessions

Response Codes

Understand all response codes