RPM is only apply to API Hashing Service. but legacy api RPM is no limit.
The explaination a bit technical and my english is not so good hope u guy can understand.
Inside Game all the action such as scan Pokémon, catch Pokémon, power up, evolve, etc need to send REQUEST to
actual Pokémon Go Server.
Every REQUEST send to Pokémon Go’s Server, need go through a verifcation process to ensure your request is valid.
Only if the verification is pass and you request is valid, then server will response and give whatever you want.
Basically the process flow(e.g. catch Pokémon) as below:
– catch Pokémon action–> Hash request + catch api –> (Pokémon Go Server) perform catch
–> (Pokémon Go Server) perform catch and send response -> (app) catch result.
In Legacy Api (0.45), The Hash Algorithm is done inside the App.
(app) catch Pokémon -> (app) hash + (app) catch api -> (Pokémon Go Server) perform catch
In Api Hashing Service by PF (0.51) [paid model], The way of perform has a bit changes in the middle
(app) catch Pokémon -> (Hash Service)request hash and wait it hash result + (app) catch api –> Pokémon Go server.
Hash Service implement the plan with RPM services (150RPM, 500RPM, etc) with the license key.
For example: 150 RPM License key
– you number of hash request for that API key in a minutes is maximum 150.
– IF you request has been exceed 150, during Hash request, the Hash Service will reject give the Hast Result in THAT particular minute ONLY.
(that mean you cannot perform any ACTION )
– But after the next minute, Hash Service will resume back service and reset counting how many request you has been ask.
OK, clear ? Now can answer the usage for the RPM tracker below the app now . hehe
Example for the text below that app:
RPM: 6 (364ms) [error message]
6 = number of REQUEST has been sent to Api Hash Services
(364ms) = how fast the Api Hash Service reply back to app ( 1000 ms = 1 second)
[error message] = Error mesasge reply from Api Hash Service that cause the hash failure.
So the app cannot proceed to send the action to Pokémon Go Server.
Possible causes may due to Hash Server problem or Exceed the RPM if your API key has been used by many devices at the same time.
If Blank that mean not error from Hash Service