Thank you for the response. We're thinking through a use case and exploring options.
The underdeveloped use case I'm thinking of uses the API to help create a preservation copy of Aviary resources with the copy stored outside Aviary. The rough idea might look like: once a month determine what is new or changed within the time period and update the preservation copy. In this use case, the minimum could be a GET request for all audit data with paginated results. A bit better, results sorted by timestamp. Even better, the option to filter by a begin and end date range. In the rough preservation use case, a script leverages the "asset type" and "asset id" from the activity/audit log to lookup the associated resource id then uses the API to capture the resource along with associated components and stores in the new/changed assets in the preservation store.
I could also image given an asset id wanting to know the change history, the use case Kevin mentions.
Cheers,
Jeff