From 343260dc5282f34c742cc221c4dda85959808818 Mon Sep 17 00:00:00 2001 From: Ouroboros Chrysopoeia Date: Sat, 22 Aug 2020 22:05:55 -0400 Subject: [PATCH] Remove obsolete references for rate limits --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index d54d772..5e69849 100644 --- a/README.md +++ b/README.md @@ -26,15 +26,15 @@ It can on rare occasions be necessary to have the confirmation email resent. * Enter password and click Generate Token. #### Rate limits -The following are the known rate limits per token: -* Per minute: 100 (presumably for status 200 or 201) [[ref]](https://dev.bitly.com/v4/#section/Rate-Limiting) -* Per hour: 1000 (presumably for status 200 or 201) [[ref]](https://dev.bitly.com/v4/#section/Rate-Limiting) -* Per month: 1000 (presumably for status 201 only) [[ref] (requires API use)](https://nullrefer.com/?https://dev.bitly.com/api-reference#getPlanLimits) +The following have historically been the rate limits per token: +* Per minute: 100 (presumably for status 200 or 201) +* Per hour: 1000 (presumably for status 200 or 201) +* Per month: 1000 (presumably for status 201 only) Bitly sends a monthly email if if 50% of the account's usage limit for new short links is exceeded for the calendar month. If this email is received, it is suggested to immediately obtain and add additional tokens to the pool used by this package. As follows, it is preferable to stay under 50% of the usage limit by having a sufficiently big pool of tokens. -It is possible to monitor the usage via the `.usage()` method as shown in the examples. +It is possible to monitor the usage via the **`.usage()`** method as shown in the examples. It is unknown what the per-IP rate limit is, if any.