Proxy Configuration
Every LinkedIn account connected through We-Link requires a proxy. The proxy is used during login and for all subsequent requests to LinkedIn, ensuring each account operates from a consistent IP address.
Exactly one proxy method must be provided when calling the login endpoint. If no valid proxy configuration is supplied, the request will be rejected.
Proxy Methods
We-Link supports two proxy options:
| Method | Description | Managed by |
|---|---|---|
| Internal Proxy (recommended) | We-Link assigns a geo-matched, high-quality residential proxy | We-Link |
| Customer Proxy | You provide your own proxy credentials | You |
Internal Proxy (Recommended)
We-Link automatically assigns a dedicated, localized IP address based on the country code you specify. This is the simplest option — no infrastructure to manage on your side.
Required Field
| Field | Type | Description |
|---|---|---|
location | string | Supported country code (e.g., "US", "IN", "GB") |
Supported Locations
View all 69 supported country codes
| Code | Country | Code | Country | Code | Country | Code | Country |
|---|---|---|---|---|---|---|---|
AE | United Arab Emirates | CR | Costa Rica | ID | Indonesia | NL | Netherlands |
AL | Albania | CY | Cyprus | IL | Israel | NZ | New Zealand |
AM | Armenia | DE | Germany | IM | Isle of Man | OM | Oman |
AR | Argentina | EE | Estonia | IN | India | PH | Philippines |
AT | Austria | EG | Egypt | IS | Iceland | PK | Pakistan |
AU | Australia | ES | Spain | IT | Italy | PL | Poland |
AZ | Azerbaijan | FI | Finland | JP | Japan | PT | Portugal |
BD | Bangladesh | FR | France | JO | Jordan | RS | Serbia |
BE | Belgium | GB | United Kingdom | KE | Kenya | SA | Saudi Arabia |
BG | Bulgaria | GE | Georgia | KZ | Kazakhstan | SE | Sweden |
BO | Bolivia | GR | Greece | LK | Sri Lanka | SG | Singapore |
BR | Brazil | HK | Hong Kong | LT | Lithuania | SK | Slovakia |
BY | Belarus | HR | Croatia | LV | Latvia | SL | Sierra Leone |
CA | Canada | HU | Hungary | MD | Moldova | TN | Tunisia |
CH | Switzerland | MK | North Macedonia | TR | Turkey | ||
CL | Chile | MX | Mexico | UA | Ukraine | ||
CN | China | MY | Malaysia | US | United States | ||
NG | Nigeria | UZ | Uzbekistan | ||||
ZA | South Africa |
Example
{
"email": "user@example.com",
"password": "securePassword123",
"twoFASecret": "JBSWY3DPEHPK3PXP",
"proxy": {
"location": "US"
}
}
How It Works
- We-Link searches for an available proxy in the requested location.
- If available, the proxy is assigned to the account automatically.
- If no proxy is available for that location, the request fails with a
400error:
{
"message": "No proxy available for location: {US}",
"error": "Bad Request",
"statusCode": 400
}
Billing & Location
If you log in using one location and later log in again with a different location, a new proxy will be allocated. Since proxy allocation is location-based, this may result in additional charges.
Always provide the correct location to avoid unnecessary credit consumption.
Customer Proxy
Provide your own proxy credentials if you have dedicated infrastructure or need a specific IP address.
Required Fields
| Field | Type | Description |
|---|---|---|
host | string | Proxy host or IP address |
port | number | Proxy port |
username | string | Proxy username |
password | string | Proxy password |
Example
{
"email": "user@example.com",
"password": "securePassword123",
"twoFASecret": "JBSWY3DPEHPK3PXP",
"proxy": {
"host": "192.168.1.1",
"port": 8080,
"username": "proxy_user",
"password": "proxy_password"
}
}
Behavior
- The proxy is validated before the login session starts.
- If validation fails, login is rejected.
- We-Link does not manage lifecycle or billing for customer-provided proxies — you are responsible for uptime and rotation.
Proxy Validation
All proxies — internal or customer-provided — are validated before initiating a login session:
- We-Link performs an initial proxy connectivity check.
- If it fails, a secondary validation attempt is made automatically.
- If both attempts fail, the request is rejected:
{
"statusCode": 500,
"message": "Second proxy attempt failed, management notified"
}
Monitoring Proxy Health
Once an account is connected, you can check and recover the proxy at any time using the proxy_status endpoint.
Endpoint: POST /api/v1/proxy_status
{
"accountId": "1234ab5678290....",
"reactivate": true
}
Response:
{
"message": "Proxy is active"
}
Setting "reactivate": true attempts to reactivate the proxy if it's in an error state.
Switching Proxies
You can change the proxy for an existing account without disconnecting it:
| Endpoint | Description |
|---|---|
POST /api/v1/switch_to_internal_proxy | Switch to a We-Link internal proxy |
POST /api/v1/rotate_internal_proxy | Rotate to a new internal proxy in the same location |
POST /api/v1/switch_to_customer_proxy | Switch to your own proxy |
These endpoints are available in the API Reference.
Best Practices
- Use internal proxies unless you have a specific reason to bring your own — We-Link handles rotation, uptime, and geo-matching automatically.
- Match the proxy location to the LinkedIn account's usual login region to minimize LinkedIn security flags.
- Don't change proxy locations frequently — each location change allocates a new proxy and may incur additional charges.
- Monitor proxy health using the
proxy_statusendpoint, especially if you seePROXY_ERRORfailures in webhooks. - For customer proxies, use high-quality residential or ISP proxies — datacenter proxies are more likely to be flagged by LinkedIn.