You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 7, 2023. It is now read-only.
I was told by Blockchain.com support to submit my question as a GitHub issue to get the attention of the core maintainers, who would be better equipped to answer my question.
On blockchain.com/api, it's stated that an API key can be used to bypass the rate limit. However, the Blockchain Data API documentation doesn't contain any instructions for using an API key. I made a guess based on the Receive Payments API doc that adding it as a query string parameter called key would work, but when doing this I still got flagged for a rate limit violation.
Can you confirm whether this was the correct way to use the key with this API, or if there's even intended to be a way to bypass the rate limit with this API? If what I did was supposed to work, did I run into a bug, or is there still another higher undocumented rate limit that I need to comply with?
The text was updated successfully, but these errors were encountered:
I was told by Blockchain.com support to submit my question as a GitHub issue to get the attention of the core maintainers, who would be better equipped to answer my question.
On blockchain.com/api, it's stated that an API key can be used to bypass the rate limit. However, the Blockchain Data API documentation doesn't contain any instructions for using an API key. I made a guess based on the Receive Payments API doc that adding it as a query string parameter called
key
would work, but when doing this I still got flagged for a rate limit violation.Can you confirm whether this was the correct way to use the key with this API, or if there's even intended to be a way to bypass the rate limit with this API? If what I did was supposed to work, did I run into a bug, or is there still another higher undocumented rate limit that I need to comply with?
The text was updated successfully, but these errors were encountered: