Exceeding max requests

[charlesknipp]

When downloading more than 10 securities in parallel, the API often returns failed requests. Looking further into the matter, the HTTP response yields a 202, yet marks the requests as failed.

Upon closer inspection, the response header notes reveal that this is caused by exceeding the maximum number of get requests per minute. I think the number of status checks for longer requests is pushing the API's limits. Although it seems unlikely, since async status checks wait 30s before sending another get request.

[charlesknipp]

429bc72 increases the wait time per status check get request. Although Refinitiv advises against changing this value, I found it greatly decreases the probability of exceeding the max get requests.

[charlesknipp]

It is also worth noting that we can hit another limit via the exceeding the maximum number of extractions at any given time. I think the best course of action would be to cancel any existing jobs.

For this, I need to create 2 main functions:

1. get active jobs (and job ids)
2. cancel extraction given the job id