NPSSO management

[platinumachievements]

Just a quick question to make sure I haven't missed anything, when making a call to get users trophies how do you manage the NPSSO? I believe there is a limit of 300 calls every 15 mins? I'm trying to think of ways I can manage a lot of calls? If I had 2 users each with 300 games it will take me over 30 minutes using 1 NPSSO? Do people use multiple NPSSO or do you use another way? @Lamarcke @isFakeAccount @Hartaithan

[Lamarcke]

Hey, i'm currently using the NPSSO to log-in once, and then store the returned accessToken + refreshToken in some sort of cache, like Redis.

I then use the refreshToken to refresh the accessToken when it expires.

EDIT:
The code i'm using:
https://github.com/game-node-app/game-node-server/blob/dev/src%2Fsync%2Fpsn%2Fauth%2Fpsn-sync-auth.service.ts

[platinumachievements]

Thanks for replying, appreciate it. Cool, that's what I'm doing at the minute on the backend, mines more basic storing the details in a json and seeing if the token is in date, if not getting a new one, while I'm testing but will prob use redis once I'm happy. I'm just wondering about the limits. You ever get rate limited? Do you get your users to provide their own NPSSO?

[Lamarcke]

To be honest i don't have that many users, but i usually try to fetch the entire user library in one go to process my stuff, so i had to implement caching for each request "page", which greatly helps alleviate the problem. Again, using Redis.

I would guess this 300/15m request limit still applies?
https://andshrew.github.io/PlayStation-Trophies/#/APIv1?id=api-rate-limit

[platinumachievements]

Haha I'm probably only going to get a few users so I'm probably overthinking it lol. I'll defo have to implement some sort of cache, I haven't really used redis so that's on the todo list!

[isFakeAccount]

If I had 2 users each with 300 games it will take me over 30 minutes using 1 NPSSO?

Not necessarily. This is assuming 1 call fetches one game. But most likely one API call will fetch 50 or maybe even 200 items.

You can see this here https://github.com/isFakeAccount/psnawp/blob/master/src/psnawp_api/models/user.py. Each endpoint has different page size. So depending on what you are doing. You most likely don't need 300 API calls to fetch 300 games.

[platinumachievements]

Yeah that was probably worded wrong on my behalf, the fetching games isn't the issue, it's the fetching of user trophies for each game. It's only a couple of calls to get all the games. But seems like I'm making lots of calls to get the trophies and I'm getting a big backlog on my queue, if I'm only allowing 300 per 15 mins.

[Lamarcke]

It would probably be worth it to have that data stored in your own end. Are you using a database of any kind? You could create a table and add some updating logic that would only hit PSN's side when necessary.

[isFakeAccount]

Yeah that was probably worded wrong on my behalf, the fetching games isn't the issue, it's the fetching of user trophies for each game. It's only a couple of calls to get all the games. But seems like I'm making lots of calls to get the trophies and I'm getting a big backlog on my queue, if I'm only allowing 300 per 15 mins.

Trophies should be relatively simple as well. At least for 2 users. If you are fetching from 100s of users then it would become an issue.

Can you share your work so it easier to give more useful advice.

Also, like @Lamarcke mentioned. It might be worth caching responses.