GivePanel Reporting API: Date Filters and Common Query Behaviour

Across the Reporting API, date parameters generally align with the same logic used in the GivePanel interface when filtering by date.
​

Each endpoint filters results based on the most relevant “primary date” for that object type.

For the /registrations endpoint, the start and end parameters refer to the registration created date.

This means:

They do not relate to:

Registrations are always filtered by when the registration record was created in GivePanel.

For the /donations endpoint, the startDate and endDate parameters refer to the date the donation was made.

This means:

This aligns with how donation filtering works inside GivePanel.

Donations are filtered by the actual donation transaction date, not import time or processing time.

For the /fundraisers endpoint, date filtering refers to the fundraiser start date. (normally when the fundraiser was created)

A common issue when retrieving donations is pagination.

The API uses zero-based pagination.

This means:

If pagination starts at page=1, the first set of results may be skipped, which can lead to missing or inconsistent data.

Some fundraisers may not appear in /fundraisers?updatedAfter=... even though they exist in other queries.

This typically happens because:

To include them, use the jg=true parameter:

To retrieve a complete dataset (both types of fundraisers), you must run two requests and combine results: