Search on the PermID website stopped working at about 11.35 GMT on 1st March. All search requests are redirecting back to the home page.
@trubens
The API limitations are specified on the FAQ page.
7. Are there any restrictions on usage?We enforce daily and concurrent rate limits on the PermID.org APIs to protect our servers. The daily limit is 5,000 requests (500 for Open Calais), and the concurrent limit varies by API from 1-4 calls per second. If your use case requires higher limits for the Refinitiv Intelligent Tagging, please contact permid.feedback@lseg.com
I am not sure if it is also applied to the PermID Website. You can contact the permid.feedback@lseg.com to confirm this.
Thank you for reaching out to us.
I am testing it and it is working fine.
Thanks for the prompt response. I tried again on multiple browsers and still not working. I then tried on my phone over a 4G connection and it DOES work, both anonymously and logged in!
I then went back to my laptop and looked at the network traffic to the browser and notice I'm getting an http 429 response code (too many requests):
URL: https://permid.org/api/search?q=glencore&num=5&start=1&selected=all
Status: 429
This seems odd because I've only been doing manual searches on the website for a few hours this morning (not using the API) so no chance I've exceeded 5000 requests in the last 24 hours.
Also it seems odd that it works logged in on my phone, so it seems the quota is associated with the IP address of my laptop, My public facing IP address is currently 95.145.0.99
Could you confirm how the 5000 request quota works, and why it seems my IP address has been blocked?
Thanks.
Toby.
Two other points:
If I request a specific PermID on the website it does give me a full response, even though search is NOT working.
Earlier I tried to view https://permid.org/1-5000700978 and it was (and still is) hanging, so I wonder if there was some retry going on in the background which was incrementing towards my quota?
Enabled a VPN on my laptop and search started working, so does seem there is something going on with search quota versus IP address.
