Going forward we will need to cache some data so that we don't hammer wildapricot's api and in turn suffer from triggering wildapricot api rate limits.
In order to safely cache some data we need to support webhooks so that we can update data in the application and application's database. The first candidate for said support would be working groups. Specifically, when volunteers are added or removed from wildapricot we need to update our database. Likewise, if volunteers are added or removed via the website, we need to update wildapricot appropriately.
Going forward we will need to cache some data so that we don't hammer wildapricot's api and in turn suffer from triggering wildapricot api rate limits.
In order to safely cache some data we need to support webhooks so that we can update data in the application and application's database. The first candidate for said support would be working groups. Specifically, when volunteers are added or removed from wildapricot we need to update our database. Likewise, if volunteers are added or removed via the website, we need to update wildapricot appropriately.