0 Replies Latest reply on May 14, 2015 12:56 PM by jpadilla

    calling api with "after" query parameter doesn't return expected links->next

    jpadilla

      Submitting an API call with "after" query parameter:

      https://community.xxx.com/api/core/v3/activities?after=2015-05-13T00:00:00.000%2B0000&count=10

       

      Produces a "Links" object with "next" value of:

      https://community.xxx.com/api/core/v3/activities?fields=%40all&count=10&before=2015-05-14T13%3A45%3A25.026%2B0000


      Why is he "after" value is replaced with "before"? This ends up providing me the entire activities result set (from day 1)  if I continue to following the next link.

       

      My expectation was that the query parameter would remain as "after" and the value would be updated to retrieve the next batch of records until no "next" link is provided.

       

      Is this a bug or is my expectation not reality?

       

      My goal is to retrieve all activities that have occurred for the prior day.

       

      Thanks.