https://community.hubspot.com/t5/APIs-Integrations/Announcing-a-change-of-behavior-for-the-prev-paging-response/m-p/378142#M37181 <P>When returning a large amount of data, HubSpot endpoints frequently employ a paging mechanism, where a subset of the response data is returned, along with a <FONT face="courier new,courier">paging</FONT> object. This object contains information about how to get new pages of information.</P> <P>&nbsp;</P> <P>Currently, our endpoints always return a <FONT face="courier new,courier">prev</FONT> value in that <FONT face="courier new,courier">paging</FONT> object, even if there isn’t a previous page. In these cases, <FONT face="courier new,courier">prev</FONT> has a value of <FONT face="courier new,courier">null</FONT>, which is accurate, but unnecessary.</P> <P>&nbsp;</P> <P>Starting on January 25th, 2021, we will only include the <FONT face="courier new,courier">prev</FONT> value when there is in fact a previous page of data to return. For this to be the case, the endpoint must support reverse paging, and the current page can’t be the first. In all other cases, the <FONT face="courier new,courier">prev</FONT> value will be omitted from the <FONT face="courier new,courier">paging</FONT> object in the response.</P> <P>&nbsp;</P> <P>If you have any questions about this change, please comment here on the forum thread.</P> Mon, 12 Oct 2020 19:19:03 GMT mwelch 2020-10-12T19:19:03Z https://community.hubspot.com/t5/APIs-Integrations/Announcing-a-change-of-behavior-for-the-prev-paging-response/m-p/378142#M37181 <P>When returning a large amount of data, HubSpot endpoints frequently employ a paging mechanism, where a subset of the response data is returned, along with a <FONT face="courier new,courier">paging</FONT> object. This object contains information about how to get new pages of information.</P> <P>&nbsp;</P> <P>Currently, our endpoints always return a <FONT face="courier new,courier">prev</FONT> value in that <FONT face="courier new,courier">paging</FONT> object, even if there isn’t a previous page. In these cases, <FONT face="courier new,courier">prev</FONT> has a value of <FONT face="courier new,courier">null</FONT>, which is accurate, but unnecessary.</P> <P>&nbsp;</P> <P>Starting on January 25th, 2021, we will only include the <FONT face="courier new,courier">prev</FONT> value when there is in fact a previous page of data to return. For this to be the case, the endpoint must support reverse paging, and the current page can’t be the first. In all other cases, the <FONT face="courier new,courier">prev</FONT> value will be omitted from the <FONT face="courier new,courier">paging</FONT> object in the response.</P> <P>&nbsp;</P> <P>If you have any questions about this change, please comment here on the forum thread.</P> Mon, 12 Oct 2020 19:19:03 GMT https://community.hubspot.com/t5/APIs-Integrations/Announcing-a-change-of-behavior-for-the-prev-paging-response/m-p/378142#M37181 mwelch 2020-10-12T19:19:03Z