added header api call limits information to request result #430
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
user to control last 60 minutes amount of API calls
response, added tests and documentation
|
How does this differ from #427? |
|
Because He's only adding x-app-usage, but in my case I need x-page-usage. It's depend of the kind of your request query, facebook will increment ona value variables or the another one. If any of this six values arrives to 100, the requests to the API will be blocked. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Facebook API has to call limits you can see documentation here:
Facebook call limits
So adding this information to the result you allow api user to control the amount of queries done in the last 60 minutes