Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Throttled requets even with API key
See original GitHub issueHey, first of all, thanks for this SDK and API that we are using to build a custom NFT store! I’m having some problems using the API key, I’m getting the throttle message with API key on rinkeby and mainnet, we can make like 7 requests before throttled, and then pretty long throttle interval. We are using the /asset/ to get information about every NFT that we are listing so we can display custom info.
Is this the expected behavior? Is there any way to this differently?
Issue Analytics
- State:
- Created 2 years ago
- Comments:47
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I there any way to find out about API limits for a certain API key?
After contacting OpenSea, they confirmed this is the normal behavior and we made a proxy around it.
For the back-end part we use our key to cache requests and redistribute them to clients, and for front-end only stuff we use no api key so each user has its own throttle limits