Fixed: Performance on Registrations and Supporters Endpoints

Today we release enhancements to the above mentioned endpoints in lieu of a page cursor parameter implementation to ameliorate issues some of our larger charities encounter with the page parameter.

More efficient use of the date_from and date_to parameters is proffered as the interim solution and clients are encouraged to use them alongside the limit parameter. The idea is to while holding date_from param steady shift the value of the date_to param relative to the value returned from last record in the most recent result set and to totally ignore or stop using page parameter.

Clients who, for example, run a daily schedule to retrieve /registrations are encouraged to provide date_from=<date_previous_day> 00:00:00 and date_to=<date_previous_day> 23:59:59 with limit=100 like so:

curl --location '<https://dataapi.enthuse.com/registrations?access_token=><token>&limit=100&date_from=2025-02-10%2000%3A00%3A00&date_to=2025-02-10%2023%3A59%3A59'

Subsequent calls can then be made with:
date_from=<date_previous_day> 00:00:00 and date_to=<response’s final entry’s changed_at> with limit=100 and can carry on doing this until there are less than 100 items in the last response.

Clients who run a daily schedule to retrieve /supporters are encouraged to provide date_from=<date_previous_day> 00:00:00 and date_to=<date_previous_day> 23:59:59 with limit=100 like so:

curl --location '<https://dataapi.enthuse.com/supporter?access_token=><token>&limit=100&date_from=2025-02-05%2000%3A00%3A00&date_to=2025-02-05%2023%3A59%3A59'

Subsequent calls can then be made with:
date_from=<date_previous_day> 00:00:00 and date_to=<response’s final entry’s last_updated_at> with limit=100 and can carry on doing this until there are less than 100 items in the last response.