# SNKRS (Raffle drops)
You have the following modes available:
* (no value): normal drop mode, the one you should usually use
* `SHOCK DROP`: faster than empty mode useful to catch/run shock drops (you should be sure that a session for the given account is already available)
* `CHECKER`: check the health of your account, if it is phone number validated and also your the score that nikes assign to your address
* `EA`: check if you have an upcoming EA for this account
* `MANUAL`: just logs into your account with the given proxy and halts, it is useful if you want to manually handle a recent order or do your stuff to set up your account manually
* `SESSION`: generates a session for an existing account
* `ADDRESS`: remove all existing saved addresses and payment methods and add new ones based on your csv
* `VALIDATE`: validates your account via SMS if needed
* `ACCOUNT` : generates a new account, fills the address, the payment and... validates your account via SMS :tada:
### Tasks setup
Here is a table that explains the meaning of every field and, if applicable, a default value.
| COLUMN NAME | VALUE |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| SITE | NIKE as a value |
| MODE | Empty or one as a reported above |
| PID | Product SKU like `HJ4303-400` |
| QUANTITY | Ignore this column, leave it empty |
| DELAY | In milliseconds (e.g. 3000 for 3 seconds delay) |
| EMAIL | Account email (has to be a valid Nike account) |
| PASSWORD | Account password |
| FIRST NAME | Recipient name |
| LAST NAME | Recipient surname |
| ADDRESS LINE 1 | Recipient first address line |
| ADDRESS LINE 2 | Recipient second address line (optional) |
| HOUSE NUMBER | Recipient house no. |
| CITY | Recipient city |
| ZIPCODE | Recipient zip code |
| STATE | Recipient state |
| COUNTRY | A 2-letters country ISO Code (e.g. GB for UK)
Only non-GS regions are allowed right now.
GS module is in roadmap
|
| PHONE | With country prefix like +44123456789 |
| PAYMENT | `CC` |
| CARD HOLDER | Your card holder |
| CARD NUMBER | Card number |
| EXP MONTH | Two digits (e.g `02` or `12`) |
| EXP YEAR | Four digits (e.g. `2026)` |
| CVV | Credit card CVV |
| WEBHOOK | If empty the one set up in `settings.json` will be used |
| ENTRY WEBHOOK | If present and filled it will send a webhook for all entries that have been made successfully |
| START TIME | Empty if you want to manually start your task.
A specific time in the format hh:mm:ss like 08:50:00 to automatically start this task at the given time.
Don't worry if you recognize you put a wrong time in there. You can still manually force start it.
If you didn't put a specific time, don't forget to put MANUAL as a value if you want to avoid every task to immediately start as soon as your task file is started.
|
| ENTRY TIME | In the same format as per START TIME cell but this value refers to the specific time the entry for the draw has to be done.
You can use our wizard built into the CLI to easily generate it
You recognise you put a wrong entry time?
You can still manually click on the entry button and pepper will take care of it
|
| PROXY | You can put a specific proxy or a proxy list.
In case you using a proxy list, it has to be the exact filename, don't forget the extension name like .txt (e.g. nike.resi.txt).
If empty nike.txt will be used.
You can also run without proxy by writing localhost
|
| IMAP | When you generate sessions, Nike will sends you an 8-digit OTP code to the given email address. Put here your IMAP connection settings in the following format:
server:port:username:password
As example:
imap.mail.me.com:993::my-app-password
|
### Proxy checker
We built our own proxy checker, not to check their speed but to check if your proxies are banned on specific steps during the entry flow.
During our tests we identified a lot of blocks at entry step and at payment one.
Put all of your proxies inside a txt and run the proxy checker.\
\
You will be able to check which is good to go and which it isn't.
{% hint style="warning" %}
Please don't overtest it. You are invoking some sensible endpoints. Don't let your proxies to be banned by yourself.\
\
Prefer **good** ISPs over resis.
{% endhint %}
### Example taskfile
Here is an example task file:
{% file src="/files/0v9CXbtXQTMVkAXFvxDw" %}
You can edit this file by using [Rons editor](https://www.ronsplace.ca/products/ronseditor).
### Generate tasks
Now, you filled your CSV (e.g. called **nike.csv**) and you are ready for a drop.
Everything is well configured.
The day after another drop is coming.
You can of course still manually edit your CSV and change PID, SIZES and ENTRY TIME (if the drop mode is different from the previous one) but there is something more.
You can quickly edit all this infos directly via CLI by using our task generator (option 2 inside the Nike submenu).
Once started it will ask you which is the source task file to edit (you will choose **nike.csv** as per the example).
Right after it will show you all upcoming drops with the related drop date and time.
Once chosen it it will recognise also which drop method will be used (if LEO and DAN) and will ask you the first entry time and the last entry time, pepper will generate all entry times for other tasks according with the value you specified for start and end entry time and the numbers of tasks you have.
You can also specify the sizes or the size range you want to run for.
Once finished a new file named **nike-pid.csv** will be generated. The `pid` will be the one you decided to run for. Also the mode for the file will be automatically set as empty.
### Account validation
`VALIDATION` and `ACCOUNT` mode needs an sms provider set up in order to validate your account.
Here is an example of configuration you should have in settings.json under nike node:
```
"nike": {
....
"validateAccountsAfterCreation": false,
"smsProvider": "smsactivate",
"smsService": "nike",
"smsRegion": "RO"
}
```
All options should be self explanatory.
Just little a note on the `smsRegion` : up to you which region you want to use.
Don't forget to set up the sms provider key as explained [here](https://docs.pepperscripts.com/getting-started/cli/settings)
### Proxies, which ones?
ISPs or DCs are always the best choice, in terms of speed and costs since you don't need to care about data usage.
Be sure to ask your provider that you need to run them on Nike drops and be sure to run the built-in proxy checker in order to check if they are unbanned (for real) on all sensitive steps that will be involved during a drop.
If you are going to run with Residentials you definitely should take care about data usage since you are billed per netwrok usage.
Since Nike website is fully loaded with images and videos this will be a money drain while using residentials. If you want to save a lot of data you can edit your `settings.json` and edit the following part:
```
"sites": {
"nike": {
"disableVideos": false,
"disableImages": false
}
}
```
You can just put what you want to disable to `true` instead of `false`.
So for example imagine you want to disable only videos but you want to keep images you can just need to do as follows:
```
"sites": {
"nike": {
"disableVideos": true,
"disableImages": false
}
}
```
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.pepperscripts.com/supported-sites-cli/snkrs-raffle-drops.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.