public-api.exceeded-api-key-allowance

2 posts / 0 new
Last post
effbiae
public-api.exceeded-api-key-allowance

what is the guideline for number of concurrent connections, or number of requests per second?

i was over-using the /marketnavigation call. recursively calling it to get nodes, then the children of the nodes, etc. caused a lot of hits in a small amount of time.

i got this:
{ errorCode: 'error.public-api.exceeded-api-key-allowance' }

then this:
Error: read ECONNRESET

effbiae
continuing with a recursive

continuing with a recursive /marketnavigation, but using a rate-limiter (in nodejs) to throttle all REST requests to 1 per 2 seconds. this seems to cause { errorCode: 'error.public-api.exceeded-api-key-allowance' } about every 30 requests.

then decreased the frequency to 1 per 2.06 seconds but that failed sooner with:

Error: read ECONNRESET
at exports._errnoException (util.js:1050:11)
at TLSWrap.onread (net.js:582:26)

decreasing to 1 per 2.6 seconds seems to operate without error*.

what if there are 10 positions to close - will it take 26 seconds to close all?

is there a dynamic approach when presented with exceed-allowance error? back off exponentially with retries?

*except just got:
Error: unexpected end of file
at Zlib._handle.onerror (zlib.js:355:17)

Log in or register to post comments