It might be a language barrier, but I don’t really understand your issue.
It sounds like you are potentially talking about storing 100 variables which seems excessive.
Therefore, to help understand your issue a bit better, can you share some details on the actual GET request and what that looks like. In particular, the parameters or body that you need to send with the request.
Do you have any documentation in relation to the API itself to help guide us?
I suspect what you mean is that you want to loop through 100 requests with different user ID’s? (But this is totally an guess and would prefer if you could clarify).
yes, it’s about looping my GET request and put there value from variable. And it can be thousands testing values. Just checking if this approach is fine (the best practice).
Stick your test data in a CSV file and use the Collection Runner.
You reference the data in the CSV file by their headers using the same way you reference any other variable. {{variableName}} so you don’t have to write any code for this. It will run your request(s) once for each line in the CSV file.
The following links show you how to work with data files.
I really wouldn’t run 10,000 requests in one go. I would probably split this into smaller CSV files and run them separately. In bunches of 500 perhaps.