Incorrect rate limit values when using app authentication
up vote
-1
down vote
favorite
Can anyone shed some insight as to why I would be seeing a different rate_limit_remaining after my Podio::filter call.
My app credentials are stored in a multidimensional area that I increment the index once Ive gotten close to the rate limit. I seem to be grabbing the wrong credentials
php podio
add a comment |
up vote
-1
down vote
favorite
Can anyone shed some insight as to why I would be seeing a different rate_limit_remaining after my Podio::filter call.
My app credentials are stored in a multidimensional area that I increment the index once Ive gotten close to the rate limit. I seem to be grabbing the wrong credentials
php podio
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
Can anyone shed some insight as to why I would be seeing a different rate_limit_remaining after my Podio::filter call.
My app credentials are stored in a multidimensional area that I increment the index once Ive gotten close to the rate limit. I seem to be grabbing the wrong credentials
php podio
Can anyone shed some insight as to why I would be seeing a different rate_limit_remaining after my Podio::filter call.
My app credentials are stored in a multidimensional area that I increment the index once Ive gotten close to the rate limit. I seem to be grabbing the wrong credentials
php podio
php podio
asked Nov 21 at 10:19
Onome Omene
285
285
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Podio has two tiers of rate limits: normal, and rate limited calls. PodioItem::filter
is a rate limited call, which has a lower rate limit.
You can get around this by creating a saved view with your filter parameters, and using PodioItem::filter_by_view
instead. PodioItem::filter_by_view
uses your normal rate limit instead of the intensive one.
See more: https://developers.podio.com/index/limits
Also relevant is Andreas' response: https://help.podio.com/hc/en-us/community/posts/202750276-Discrepancy-in-rate-limit-reporting-
I also recall that certain API calls are restricted when using the app authentication flow, so that may be why the rate limit is switching over.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Podio has two tiers of rate limits: normal, and rate limited calls. PodioItem::filter
is a rate limited call, which has a lower rate limit.
You can get around this by creating a saved view with your filter parameters, and using PodioItem::filter_by_view
instead. PodioItem::filter_by_view
uses your normal rate limit instead of the intensive one.
See more: https://developers.podio.com/index/limits
Also relevant is Andreas' response: https://help.podio.com/hc/en-us/community/posts/202750276-Discrepancy-in-rate-limit-reporting-
I also recall that certain API calls are restricted when using the app authentication flow, so that may be why the rate limit is switching over.
add a comment |
up vote
0
down vote
Podio has two tiers of rate limits: normal, and rate limited calls. PodioItem::filter
is a rate limited call, which has a lower rate limit.
You can get around this by creating a saved view with your filter parameters, and using PodioItem::filter_by_view
instead. PodioItem::filter_by_view
uses your normal rate limit instead of the intensive one.
See more: https://developers.podio.com/index/limits
Also relevant is Andreas' response: https://help.podio.com/hc/en-us/community/posts/202750276-Discrepancy-in-rate-limit-reporting-
I also recall that certain API calls are restricted when using the app authentication flow, so that may be why the rate limit is switching over.
add a comment |
up vote
0
down vote
up vote
0
down vote
Podio has two tiers of rate limits: normal, and rate limited calls. PodioItem::filter
is a rate limited call, which has a lower rate limit.
You can get around this by creating a saved view with your filter parameters, and using PodioItem::filter_by_view
instead. PodioItem::filter_by_view
uses your normal rate limit instead of the intensive one.
See more: https://developers.podio.com/index/limits
Also relevant is Andreas' response: https://help.podio.com/hc/en-us/community/posts/202750276-Discrepancy-in-rate-limit-reporting-
I also recall that certain API calls are restricted when using the app authentication flow, so that may be why the rate limit is switching over.
Podio has two tiers of rate limits: normal, and rate limited calls. PodioItem::filter
is a rate limited call, which has a lower rate limit.
You can get around this by creating a saved view with your filter parameters, and using PodioItem::filter_by_view
instead. PodioItem::filter_by_view
uses your normal rate limit instead of the intensive one.
See more: https://developers.podio.com/index/limits
Also relevant is Andreas' response: https://help.podio.com/hc/en-us/community/posts/202750276-Discrepancy-in-rate-limit-reporting-
I also recall that certain API calls are restricted when using the app authentication flow, so that may be why the rate limit is switching over.
edited Nov 21 at 21:32
answered Nov 21 at 19:47
Nathanael Bennett
646
646
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53409858%2fincorrect-rate-limit-values-when-using-app-authentication%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown