Smartproxy Help Center

Welcome to the Smartproxy developer hub. You'll find comprehensive guides and documentation to help you start working with proxies as quickly as possible, as well as support if you get stuck. Let's jump right in!

Documentation

Nike Shoe Bot

Getting the proxies

  1. Log in to our dashboard and navigate to the Proxy Server page
  2. Select the country you wish to get the IPs from and the Sticky session type and you will see which ports can be used to connect to the specified proxies. Moreover, you can use Download this list to get a list of proxy endpoints you can input into your bot.
  3. If you are using user:pass authentication, you will need to add :username:password to each line of the generated endpoints list, for example:

gate.smartproxy.com:10000:username:password
gate.smartproxy.com:10001:username:password
gate.smartproxy.com:10002:username:password
And so on.

Alternatively, you can also use Whitelisted IP authentication with our Residential proxies. Adding your proxy username and password would not be necessary then if you run your bot from a whitelisted IP address.

You can learn more about our authentication methods here

Getting a proxy list for your sneaker bot in the dashboard

Configuring proxies on Nike Shoe Bot

  1. To setup proxies in Nike Shoe Bot go to Proxies tab and click 'Add Proxy List'

Nike Shoe Bot add proxy list

  1. Paste the generated proxy endpoint list into the pop-up.
    a) If you use whitelist IP authentication you can simply paste it like this:

Nike Shoe Bot proxy list with whitelisted IP

b) Otherwise you will need to use your sub-user username:password authentication

Nike Shoe Bot proxy list with authentication

  1. When you create a task for your desired shoe, select your created proxy list

Nike Shoe Bot select proxy list for the task

Updated 2 months ago


What's Next

For tips check out our sneaker cheat sheet as well

Sneakerhead cheatsheet

Nike Shoe Bot


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.