Frame.io supports and maintains Audit Logs for the vast majority of activities taken in its applications. This includes both basic CRUD on core resources, and some special abstractions (e.g. AssetVersioned).
Frame.io Audit Logs are available via API for a rolling window of 30 days, after which they are moved into cold storage. Therefore, if you want to maintain a long history of Frame.io events, please ensure you’re storing historical log data independently.
Only Account Admins may access the Audit Logs for an Account, and all calls to the Audit Logs endpoint must be scoped to an account_id as follows:
Audit Log responses all have a similar format:
Audit Log response data can be fairly verbose, so make sure you’re familiar with pagination!
Audit Logs support a variety of filters, including date ranges. Unlike Frame.io’s Search endpoints, filters can be sent only as GET query string params.
Filters all follow the same formatting:
Currently, Audit Logs support one value per filter type. If you supply two filters of the same type (e.g. filter[action]=ActionOne&filter[action]=ActionTwo), the second filter will take precedence.
The key filter types for culling and navigating Audit Logs are:
Filters all follow a similar format, as outlined above. Below are a handful of examples target at specific use cases that can help you get started.
Date ranges are a slightly special case, in that it’s necessary to specify both the inserted_at datetime value, and the operation to apply to that datetime.
Accordingly, date range queries will always have two filter elements, each of which will itself be nested beside an [inserted_at] parameter.
Supported operations include: