|
| 1 | +--- |
| 2 | +kind:change |
| 3 | +title:API Abuse Rate Limit Responses |
| 4 | +created_at:2014-11-31 |
| 5 | +author_name:bhuga |
| 6 | +--- |
| 7 | + |
| 8 | +GitHub.com handles a huge number of abusive posts every day, largely without |
| 9 | +issue. No classifier is perfect, though, and we occasionally misidentify |
| 10 | +legitimate content and prevent its creation. In the case of API requests triggering |
| 11 | +abuse detection, we've decided to expose the rare case of a false positive so |
| 12 | +that integrators receive an informative message and can predict how to respond. |
| 13 | + |
| 14 | +Because some kinds of abuse prevention result in temporary bans, we are |
| 15 | +re-using the same 403 Forbidden response that existing applications receive |
| 16 | +when exceeding the normal[API Rate Limits]. Both situations require the |
| 17 | +application to wait before continuing. |
| 18 | + |
| 19 | +Please read the documentation on the new[Abuse Rate Limit Responses]. If you |
| 20 | +have any feedback or questions, please don't hesistate to[contact] us. |
| 21 | + |
| 22 | +[API Rate Limits]:/v3/#rate-limiting |
| 23 | +[Abuse Rate Limit Responses]:/v3/#abuse-rate-limits |
| 24 | +[contact]:https://github.com/contact?form[subject]=API+Abuse+Rate+Limits |
