The pledges you are able to fetch might be filtered by your service account's permissions, the organization you represent and the filters you have applied.

The collection you are paginating is sorted by creation datetime, descending. This means that the first page contains the most recently created pledges.

Fetching newly released pledges periodically

When you are retrieving recently released pledges using the releasedAfter-filter, one thing to keep in mind is not to store the last cursor as the starting point for retrieving tomorrow's results.

When pledges are created/submitted, they are released after a cooling down period, to allow for proper verification. However the returned collection you are paginating is sorted by creation datetime, this means that newly released pledges were previously not returned but might get added to the collection BEFORE your current cursor, which might result in you missing out on pledges.

Therefor we recommend storing the date and time you last fetched, and use that next time as the releasedAfter-filter value, instead of the last cursor.

First day: retrieve until pageInfo.hasNextPage is false in the response, and afterwards store the date and time of now, to be the releasedAfter-value for tomorrow.
- first page: /api/v1/pledges?releasedAfter=[initial]&first=50
- second page: /api/v1/pledges?releasedAfter=[initial]&first=10&after=41222ef7-a861-4bbd-ae93-2f645336b85d
- ...
- last page: /api/v1/pledges?releasedAfter=[initial]&first=10&after=10d303b1-4eca-4db4-9ae7-7cd65f98a5b5
Second day: retrieve all released after the previous datetime you fetched, retrieve until pageInfo.hasNextPage is false in the response, and afterwards store the date and time of the last pledge you received.
- first page: /api/v1/pledges?releasedAfter=[previousDay]&first=50
- second page: /api/v1/pledges?releasedAfter=[previousDay]&first=10&after=bd82f150-a797-4d9f-af09-c3ea06964e9d
- ...
- last page: /api/v1/pledges?releasedAfter=[previousDay]&first=10&after=3c53b11a-adef-4dc1-90d7-c23dc0108492
etc.

43:T90f,

The pledges you are able to fetch might be filtered by your service account's permissions, the organization you represent and the filters you have applied.

The collection you are paginating is sorted by creation datetime, descending. This means that the first page contains the most recently created pledges.

Fetching newly released pledges periodically

When you are retrieving recently released pledges using the releasedAfter-filter, one thing to keep in mind is not to store the last cursor as the starting point for retrieving tomorrow's results.

When pledges are created/submitted, they are released after a cooling down period, to allow for proper verification. However the returned collection you are paginating is sorted by creation datetime, this means that newly released pledges were previously not returned but might get added to the collection BEFORE your current cursor, which might result in you missing out on pledges.

Therefor we recommend storing the date and time you last fetched, and use that next time as the releasedAfter-filter value, instead of the last cursor.

First day: retrieve until pageInfo.hasNextPage is false in the response, and afterwards store the date and time of now, to be the releasedAfter-value for tomorrow.
Second day: retrieve all released after the previous datetime yo