Description -
Workfront API responses do not appear to return any kind of awareness of rate limits/available query capacity, yet will error with a HTTP 429 status code when we exceed that rate limit. Ideally, we should know from a prior query how much capacity remains so that we can tweak any sleep calls to maximize performance.
Why is this feature important to you -
APIs that return 429s typically inform as to rate limits and available query capacity (example: https://www.ietf.org/archive/id/draft-ietf-httpapi-ratelimit-headers-07.html). This allows the caller to add an appropriate sleep so as to (1) avoid the 429 error entirely and (2) minimize the delays between each call to only that which is required.
How would you like the feature to work -
Open to many ideas, see above.
Current Behaviour -
The Workfront API don't appear to return any rate limit details.
