Nike Reverifier/ Checker

Account Verification and API Limitation:

• Please note that there's a limited number of requests allowed to our API, with a cap of 1000 requests. Generating a single account typically consumes approximately 1-2 API requests.

• Checking the validity of accounts has minimal associated costs. However, if an account requires re-verification due to the absence of a phone number, it will consume an additional 1 API request per account.

Requirements:

To ensure smooth account verification and avoid issues, consider the following prerequisites:

• High-quality proxies are crucial to prevent Akamai or Kasada blocks on Nike and to optimize API requests. We recommend using services like Oxylabs or Byte for Nike.

• Maintain an adequate balance with your chosen SMS provider.

• Accounts generated with Skyridge benefit from a faster verification process. For accounts not created with Skyridge, please see the instructions below.

• The bot is designed to recognize if an account has been previously checked using the same email and will avoid unnecessary duplicate requests.

Checking Accounts:

• To check the validity of accounts, you'll need your 'gen_NikeAccounts.csv' file.

Account Verification Setup:

• Ensure that you do not modify the 'gen_NikeAccounts.csv' file. You can adjust the 'phone_iso' field to verify accounts with a different country.

• The bot keeps track of previously checked accounts by comparing 'gen_NikeAccounts.csv' with 'reverified_NikeAccounts.' If an account cannot be re-verified, delete it from 'reverified_NikeAccounts' and re-run 'gen_NikeAccounts.csv.'

• In some cases, the bot may be unable to verify accounts with the SMS provider. However, it will still save these accounts in 'reverified_NikeAccounts.' Accounts lacking Phone Verification (PVA) will be recorded in the CSV without a phone number.

Proxy Providers:

Proxy Provider	Works?	Additional information
Oxylabs	✅
IPRoyal	✅
PacketStream	❌	Leads to kasada and akamai blocks.
NetNut	❌	Leads sometimes to kasada and akamai blocks.

Common Errors:

Error	Usersided?	Explanation
Error logging in Account -> 401	✅	The Accountdata you submit is wrong, its either a wrong password or a wrong email.
Kasada-Error	❌	Its just a Kasada-API issue, which isn't related to the user.
Akamai-Error	❌	Its just a Akamai-API issue, which isn't related to the user.
Kasada Block -> 429	✅	Related to bad proxies.
Akamai Block -> 403	✅	Related to bad proxies.

SMS-Providers:

Provider	Supported?	Explanation
sms-bower	✅	Solid provider.
sms-activate	✅	Solid provider.
5sim	✅	Solid provider.
sms-gen	❌	Most expensive provider.
sms-man	✅
juicy	✅	Supports only a few countries but delivers high quality sims (NL, US, GB)
sms-pool	✅

For accounts that are not made with Skyridge:

This is a example gen_NikeAccounts.csv

Value	Can be random?	What happens then?
email	❌	Needs to be filled with the accounts email.
email_password	❌ Must be empty if the email forwards to your master	Leave it empty if your mails are forwarding, we only suggest to use it when you want to generate with Yahoos or AOLs (non forwarding mails with AppPassword) Its used for Nikes new 2FA at login.
password	❌	Needs to be filled with the accounts password.
firstName	✅	The bot will generate a random firstname
lastName	✅	The bot will generate a random lastame
gender	✅	The bot will set a random gender (Exact spelling is needed: WOMENS, MENS)
bday	✅	The bot will set a random birth day
bmonth	✅	The bot will set a random birth month
byear	✅	The bot will set a random birth year
country_iso	❌	Is needed for the preset/ language of the account. It can be different from phone_iso.
phone_iso	❌	Is needed for the generation for the sim country, nothing else, nike has no preset country anymore. It can be different from country_iso.
proxy	✅	leave it empty, the Skyridge will ignore this column fully.