Versions
The version object and the allowed CRUD operations on the related resource endpoint
Last updated
The version object and the allowed CRUD operations on the related resource endpoint
Last updated
Versions are associated with and are created upon every update or cancellation of the related resource to help you track the history of each resource's data changes. Resource creation is not tracked by the versions API.
Each version object contains information about the event that generated it (one of update
or destroy
), the type of resource that has been modified/deleted, the request involved, the application, worker or user that triggered the change, and more. You can find the changes history inside the changes
object which shows, for each modified attribute, the values before and after the change. Changes to non-fetchable attributes (i.e. that are not exposed to the user in the single resource object) are tracked anyway by the versions API but you won't be able to see the modified values.
At the moment, these are the resources that doesn't support versioning:
All types:
The length of time that the versions API holds your resources' changes history depends on the way the change is triggered:
Any other changes (e.g. triggered by direct API calls on any resource) are stored for 1 year.
Changes made via to other resources (e.g. updating prices, SKUs, stock items using imports, etc.) are stored for 1 month.