NEW SUPPLIER

Add provider

Add a supplier connection. Customers receive only your gateway URL.

Attach a private existing pipeline to each customer. Provider credentials remain encrypted on this server.
NEW GATEWAY ACCOUNT

Add customer

Assign the first private upstream pipeline as P1. Add more provider nicknames after creation. The customer receives only your masked gateway URL and a stable access key.
TRAFFIC CONTROL

Edit customer limit
CUSTOMER ACTIVITY

Session history

Traffic is counted per session across both proxy and forwarding API requests.

Loading sessions…
GATEWAY ACCESS

Gateway credentials

The proxy URL and API token rotate at a random time every 7–8 hours. Give the customer their stable access key once; they can use it to retrieve current credentials. Old gateway credentials stop working after rotation.

Provider and location URLProvider availability varies
The nickname is visible to the customer; the supplier name and credentials are private.Choose a country to see regions and cities.Location data: Countries States Cities Database (ODbL 1.0)Locations are a reference list; provider exit availability varies.
Use 1–32 letters or digits. Leave blank for the default country session. Reuse an ID for sticky routing; choose a new ID for another session.
Example: -pr-P1-country-US-subdivision-CA-city-los-angeles-session-200124525125. The customer can change these fields in one masked URL. Unsupported provider filters are rejected. All routes share the customer traffic limit.

Forwarding API example

Send a request to /v1/forward?url=<encoded target> with Authorization: Bearer <current gateway password>. The gateway forwards your request method and body. Add &pr=P1&country=US&subdivision=CA&city=los-angeles&session=200124525125 for a selected route.

Confirm action
PROVIDER ROUTES

Customer providers

Give each assigned provider a nickname such as P1. The customer chooses it with -pr-P1 in their masked proxy username.

Add provider route

1–24 letters, digits or underscores. Unique for this customer.