Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Raise error when API rate limit is exceeded. #43

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

vedarthk
Copy link

As mentioned in API documentation of Intercom:
http://doc.intercom.io/api/#rate-limiting

This will raise ApiRateLimitExceededError if Intercom sends Too
many requests (429) response.

Also, will it be helpful if we attach HTTP response to ApiRateLimitExceededError ?

As mentioned in API documentation of Intercom:
http://doc.intercom.io/api/#rate-limiting

This will raise `ApiRateLimitExceededError` if Intercom sends Too
many requests (429) response.
@jkeyes
Copy link
Contributor

jkeyes commented Mar 18, 2015

Hi @vedarthk. Thanks for this. Sorry about the outrageous delay in responding. The v1 code is no longer being worked on (master branch), the ongoing development is happening on the v2 branch (currently apiv2). The biggest omission from that version is error handling which I plan on resolving soon. I'll refer back to this PR when I get there. Thanks for contributing.

@vedarthk
Copy link
Author

@jkeyes ok!

@jkeyes
Copy link
Contributor

jkeyes commented Mar 28, 2015

@vedarthk I've added rate limiting support and followed how the intercom-ruby library did it. The code is all in the apiv2 branch. I have to perform a documentation review next, and when that is complete, I'll be pushing a release to PyPI. Let me know if you have any feedback. Thanks.

@vedarthk
Copy link
Author

@jkeyes great, will update once released.

@jkeyes
Copy link
Contributor

jkeyes commented Mar 29, 2015

@jkeyes jkeyes closed this Mar 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants