Required token scope (origin)

• artifacts:read

Required token scope (access_token)

• artifacts:write_metrics

Required token scope

• artifacts:read

• artifacts:write

Version metrics describe the history of user interaction with Artifact Versions. There is presently 1 type of action: access_count. This describes the number of times an experiment has been launched by a different user. Client applications are responsible for properly notifying Trovi when these events happen.

Required token scope

• artifacts:read

Required token scope

• artifacts:read

• artifacts:write

Functions the same as , but requires the Artifact UUID and version slug for a faster lookup.

Required token scope

• artifacts:read

Artifacts have ordered versions to distinguish between changes over time. The version endpoints are how you can create a new version, or delete an existing one.

Sometimes, users may wish to move their stored contents to a different platform (backend). We offer endpoints to accomplish this. One way we use this endpoint is to allow users to upload contents to our object storage, and then later allow users to request a DOI. When this happens, we migrate their content from the object storage backend to Zenodo.

Required token scope

• artifacts:write