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



enter image description here










share|improve this question


























    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



    enter image description here










    share|improve this question
























      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



      enter image description here










      share|improve this question













      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



      enter image description here







      php podio






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 21 at 10:19









      Onome Omene

      285




      285
























          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.






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            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

























            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.






            share|improve this answer



























              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.






              share|improve this answer

























                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.






                share|improve this answer














                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.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Nov 21 at 21:32

























                answered Nov 21 at 19:47









                Nathanael Bennett

                646




                646






























                    draft saved

                    draft discarded




















































                    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.




                    draft saved


                    draft discarded














                    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





















































                    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







                    Popular posts from this blog

                    Berounka

                    Sphinx de Gizeh

                    Different font size/position of beamer's navigation symbols template's content depending on regular/plain...