Nike Clip Checker

Account Re-Login Module:

  • It's important to note that there's a limitation on the number of requests to our API, capped at 1000 requests. Typically, re-logging an account requires approximately 1-2 API requests.

  • Checking accounts with an active Skyridge Session incurs minimal costs.

  • We recommend not running this module frequently, especially not right before a drop. Its primary purpose is to check your accounts following a Nike banwave.

  • After running the module a second time, you can be almost certain that the accounts are clipped. It's unclear if Nike will unlock them, so it's usually better to obtain new accounts.

Requirements:

  • To ensure a smooth process, please make sure you have the following:

    • Reliable Proxies: High-quality proxies are essential to prevent Akamai or Kasada blocks on Nike and to optimize API requests. We suggest using services like Oxylabs or Byte for Nike.

    • Accounts Made with Skyridge: The process is faster for accounts generated with Skyridge. If the accounts were not created with Skyridge, follow the instructions below.

Account Checking Process:

  • The bot checks if you've already checked an account with the same email address and avoids duplicating requests.

  • To check accounts, you'll need to have your 'gen_NikeAccounts.csv' file.

Managing Checked Accounts:

  • The bot remembers which accounts have been previously checked by comparing 'gen_NikeAccounts.csv' with 'checked_NikeAccounts.' If you wish to re-check an account, simply delete it from 'checked_NikeAccounts' and rerun 'gen_NikeAccounts.csv.'

  • Accounts that have been checked will appear in 'checked_NikeAccounts.csv' with their status recorded in the 'status' column.

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.

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.

Last updated