After many thousands of successful POST requests to this endpoint I am getting a 403 error now. Is there a rate limit that we have surpassed? We have to match ~20 million records to the PermID, and have matched ~2 million before getting that error.
@quantip
Thank you for reaching out to us.
I found the following limits on the FAQ of the Open PermID API.
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 LSEG Intelligent Tagging, please contact permid.feedback@lseg.com…How do I use Record Matching?If you have your own universe of organizations and instruments, the record matching service allows you to upload up to 1,000 of your records to return PermIDs for each one. To use record matching, you need to download the provided template, include name, ticker, RIC, and any other fields, and then upload the template to get your matches.
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 LSEG Intelligent Tagging, please contact permid.feedback@lseg.com
…
How do I use Record Matching?
If you have your own universe of organizations and instruments, the record matching service allows you to upload up to 1,000 of your records to return PermIDs for each one. To use record matching, you need to download the provided template, include name, ticker, RIC, and any other fields, and then upload the template to get your matches.
For anyone stumbling upon the same issue:
This seems to have been caused by some ill-formed "Website" strings in the POST data.