Rate Limiting

Starting with version 2.1.0, IEXSharp will automatically rate limit if you send requests too quickly. This is done with an exponential back-off strategy when a 429 HTTP code is returned by IEX. This is the reason that Polly is now a dependency.

Starting with version 2.2.0, there are additional rate limiting options, which can be specified using RetryPolicy:

• Manual: No rate limiting, and pass errors through to the IEXResponse.ErrorMessage property
• NoWait: No rate limiting, but eat error messages and print to Debug console instead
• Linear: Linear backoff policy, which starts at 250ms and increases linearly with each successive "error 429" or "ServiceUnavailable". Eats error messages and prints to Debug console instead
• Exponential: Exponential backoff policy, which starts at 250ms and increases exponentially with each successive "error 429" or "ServiceUnavailable". Eats error messages and prints to Debug console instead