Versions
The version object and the allowed CRUD operations on the related resource endpoint
Versions are associated with almost all the resources 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 change history inside the changes
object which shows, for each modified attribute, the values before and after the change.
Non-versionable resources
At the moment, these are the resources that doesn't support versioning:
Version history storage
Changes triggered by direct API calls on any resource are stored for 1 year.
Changes made via imports to other resources (e.g. updating prices, SKUs, stock items using imports, etc.) are not versioned at the moment. They are included in the recently released event stream (enterprise only). Non-enterprise customers can track those changes by fetching the event stores of each single resource.
Last updated