# Pledges pagination does not maintain parameters

**URL:** <https://www.patreondevelopers.com/t/pledges-pagination-does-not-maintain-parameters/187>\
**Category:** API Feedback\
**Created:** [January 1, 2018, 12:46am UTC](https://www.patreondevelopers.com/t/pledges-pagination-does-not-maintain-parameters/187 "2018-01-01T00:46:39Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bilge](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/bilge/32/89_2.png) [@Bilge](https://www.patreondevelopers.com/u/Bilge)\
**Post date:** [January 1, 2018, 12:46am UTC](https://www.patreondevelopers.com/t/pledges-pagination-does-not-maintain-parameters/187/1 "2018-01-01T00:46:39Z")

</div>

The documentation suggests a typical pledge call should look like the following: `GET https://www.patreon.com/api/oauth2/api/campaigns/<campaign_id>/pledges?include=patron.null`. Note in particular, the `include=patron.null` parameter. This appears to be entirely undocumented, but including this parameter appears to have the effect of excluding non-pledge related information from the response, significantly reducing noise and data size. This is great, except that the parameter is not persisted in either the `first` or `next` pagination links.

That is, following either of the pagination links in the response drops the `include=patron.null` parameter, causing the response format to change. It should be considered strictly incorrect for an API to return a different data format for different pages of the same request, yet this is exactly what is happening presently.

---

<div class="post-metadata">

**Author:** ![jeffrey](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/jeffrey/32/8_2.png) [@jeffrey](https://www.patreondevelopers.com/u/jeffrey)\
**Post date:** [January 3, 2018, 10:34pm UTC](https://www.patreondevelopers.com/t/pledges-pagination-does-not-maintain-parameters/187/2 "2018-01-03T22:34:07Z")

</div>

Hi Bilge,

Super sorry about this. We will add documentation about using `.null` to prevent following relationships.

With regards to your second point, you are completely correct that pagination should maintain the query parameters. However, for legacy reasons, doing so causes a bug in certain API requests. The fix is pending an overhaul (currently in the planning stage) to how we perform pagination in general.

Best,  
Jeffrey

---

<div class="post-metadata">

**Author:** ![Bilge](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/bilge/32/89_2.png) [@Bilge](https://www.patreondevelopers.com/u/Bilge)\
**Post date:** [January 3, 2018, 10:50pm UTC](https://www.patreondevelopers.com/t/pledges-pagination-does-not-maintain-parameters/187/3 "2018-01-03T22:50:29Z")

</div>

I’m glad to hear of your commitment to better documentation, backwards compatibility as well as providing a better solution. Good luck!

---

<div class="post-metadata">

**Author:** ![jeffrey](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/jeffrey/32/8_2.png) [@jeffrey](https://www.patreondevelopers.com/u/jeffrey)\
**Post date:** [January 4, 2018, 12:19am UTC](https://www.patreondevelopers.com/t/pledges-pagination-does-not-maintain-parameters/187/4 "2018-01-04T00:19:16Z")

</div>

Added some documentation here: [https://docs.patreon.com/#requesting-specific-data](https://docs.patreon.com/#requesting-specific-data)

Thanks for your feedback, it’s very much appreciated.

---

<div class="post-metadata">

**Author:** ![Bilge](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/bilge/32/89_2.png) [@Bilge](https://www.patreondevelopers.com/u/Bilge)\
**Post date:** [January 4, 2018, 3:28am UTC](https://www.patreondevelopers.com/t/pledges-pagination-does-not-maintain-parameters/187/5 "2018-01-04T03:28:14Z")

</div>

Thanks, that documentation looks like it was sorely needed. Great clarification for things I had inferred and also revealing some new tricks like the explicit mode for resource inclusion.