Background: I have a user database with id, displayname, twitchname and update it once per day. Since users are allowed to change their names it is difficult to update their infos with the wrong twitchname (also you don’t get 'non existent usernames with the 1st curl). so i update it with their id and right now i have to make an api call for every single user.
I also work on something similar and with the new id as primary key, it would be nice to have something like that. Updating the twitchnames of users is a great deal since the new system of usernamechanges are enabled.
If this is just to update any usernames that might have been changed, rather than using an ID and looking up 1 user at a time, can you not just use the first method you mentioned with usernames? If you request users a,b,c,d etc… and only get back a,b and d, you know c must have changed and then can do a single lookup using the stored ID you have for that old username to retrieve their new username. It’s not perfect, but it’s less calls that doing it 1 user at a time.
Would be an idea, thanks, but the other way would be nicer
So it’s a bit tricky if i request 100 users, get only 97 back and check which 3 ids i didnt get. it’s definitly a workaround, but expanding the endpoint would also be nice.