We're working to track this down. Both of your keys appear valid and should be working. Updates ASAP. Latency from key issuance should be seconds at the most.
This is resolved. Some caches were not playing together nicely. Even though we've solved the "never goes active" problem - it's probably still best to allow 5-10 minutes after the issuance of the key to give it time to propagate.
I'm getting this error too sporadically. When trying to submit multiple requests sequentially, about every 10th request receives the 403 Error message. Is there a limit to the number of requests that are submitted per second?
Yep - we're throttling at the API key level to 2 transactions per second / 50,000 transactions per day during our shakedown cruise. We plan to increase the maximum submission rate in the reasonably near future.
I just obtained my API key. I get "403 Developer Inactive". Is there some latency or what could I have done wrong?
CalEvans – 1 year ago
I get the same error. Anyone reading this?
=C=
Tom Tague – 1 year ago
glebleu & CalEvans:
We're working to track this down. Both of your keys appear valid and should be working. Updates ASAP. Latency from key issuance should be seconds at the most.
Regards,
Tom Tague – 1 year ago
All:
While we're tracking this down I'm going to share a temporary key. This key will only remain active until we've solved the 403 problem.
It has an increased QPS limit and a daily limit of 100K transactions. Please be kind and use it only for testing purposes.
8t6x2fux6pjmmu8k2tkzm3yv
Tom Tague – 1 year ago
** 403 Error **
This is resolved. Some caches were not playing together nicely. Even though we've solved the "never goes active" problem - it's probably still best to allow 5-10 minutes after the issuance of the key to give it time to propagate.
Regards,
AlexG – 1 year ago
I'm getting this error too sporadically. When trying to submit multiple requests sequentially, about every 10th request receives the 403 Error message. Is there a limit to the number of requests that are submitted per second?
Tom Tague – 1 year ago
AlexG:
Yep - we're throttling at the API key level to 2 transactions per second / 50,000 transactions per day during our shakedown cruise. We plan to increase the maximum submission rate in the reasonably near future.
Regards,
Nakul Aggarwal – 1 year ago
I got my key yesterday, but I am still getting 403 :(. Even the above mentioned temp. key is giving same error.
AlexG – 1 year ago
Tom, thanks that's what I figured. I'll step back the requests.
Tom Tague – 1 year ago
Nakul:
Please try one of the submission tools in the Gallery with your key so we can nail down if this is a key or a call problem:
Regards,