Skip to content
Getting Started
/
/
/
Complete Upload

API Endpoint Reference (1.5)

Tenovos has introduced version 1.5 to provide non-breaking improvements over previous versions.

Key Changes:

  • Authentication Standards now include OAuth2 code flow.
  • Client ID is no longer required to be passed when requesting an Authorization token using our Standard Auth from v1.4
  • New endpoints have been added and will continue to be added until v2 is generally available to all customers.
    • Adaptive Template endpoints
    • A new Get Asset endpoint with a simplified Response
    • A new Create Asset endpoint with simplified payloads for the Request and Response
    • A new Update Asset endpoint with simplified payloads for the Request and Response
    • Metadata Admin API endpoints for managing Attributes, Groups, and Templates
  • We've made some performance improvements to most endpoints
Find out more about Tenovos
Download OpenAPI description
Download OpenAPI spec (YAML)
Download OpenAPI spec (JSON)
Overview
E-mail
product@tenovos.com
License
Tenovos Active Story Management
Terms of Service
Languages
Servers
https://api.uat.tenovos.io/v1
https://api.tenovos.io/v1

ACTIONS

Invoke the Action API to retrieve information about invoked Actions.

Operations

ADAPTIVE TEMPLATES

Invoke the API to retrieve information about invoked Actions.

Operations

ASSETS

Invoke the Asset API to create, retrieve, manipulate, and share Assets. This API also provides operations to manage Asset relationships and download Asset content.

Operations

Promote Asset Version

Request

Promote an existing version of an Asset to be its current version. The Asset is identified by an Object ID or File ID in the request path; the version to promote is identified by the fileId in the request body.

Promoting a version creates a new current version from the nominated one, and carries the Asset's existing collection memberships and relationships onto it.

The user requesting the promotion must have access to the Asset.

Note on response shape: the data property carries the newly created asset-version record. Its fields are not enumerated in the handler's type definitions, so they are not documented here — see GET /asset/{id} for the Asset shape.

Security
ApiKeyAuth or BasicAuth
Path
idstringrequired

Object ID or File ID of the asset whose version is being promoted.

Headers
X-API-Keystringrequired

Customer-specific API key required to invoke API.

Authorizationstringrequired

Provided by Authentication Token creation operation

Content-Typestringrequired
Value"application/json"
Bodyapplication/jsonrequired
fileIdstringrequired

File ID of the existing version to promote to current.

Example: "8cd2c221-6a91-4dc6-9379-d55dca9d5313"
curl -i -X POST \
  'https://api.uat.tenovos.io/v1/asset/{id}/version/promote' \
  -H 'Authorization: string' \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: YOUR_API_KEY_HERE' \
  -d '{
    "fileId": "8cd2c221-6a91-4dc6-9379-d55dca9d5313"
  }'

Responses

Asset version promoted successfully.

Bodyapplication/json
statusstring
Example: "success"
messagestring
Example: "Asset version promoted successfully"
dataobject

The newly created asset-version record. Field-level shape is not declared in the handler's types; see GET /asset/{id} for the Asset shape.

Response
application/json
{
  "status": "success",
  "message": "Asset version promoted successfully"
}

Complete Upload

Request

Complete/Abort multipart upload once all parts are uploaded. This endpoint must be called after creating asset when the file is sent in chunks of 100MB each. For files 100MB or less in size this operation is not needed.

Average Response Time: 1310ms

Security
ApiKeyAuth or BasicAuth
Headers
X-API-Keystringrequired

Customer-specific API key required to invoke API.

Authorizationstringrequired

Provided by Authentication Token creation operation

Content-Typestringrequired
Value"application/json"
Bodyapplication/jsonrequired

The Request Body must be a JSON array.

fileIdstring(uuid)
filenamestring
filesizeinteger
Example: 335226108
actionstring

Either complete or abort as the action to finalize the multipart upload. This field is case sensitive.

Enum"complete""abort"
Example: "complete"
originalFileIdstring(uuid)
uploadIdstring
Example: "gR5XHJZpuDv8UizdpSGuwONje0GbMHnCWXS5zTTVkyVINURV6iraWLhpM7Sy7oy65utAgPcm2FfM4fRp4oVga4ggEzD811aS1tke_F0iIIXX1kV7m6UouytsNE0oL8fzo2Zr2JCqwRyhFTXp98zjdQ--"
partsArray of objects(AssetMultipartUploadRequest_parts)
curl -i -X POST \
  https://api.uat.tenovos.io/v1/asset/complete \
  -H 'Authorization: string' \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: YOUR_API_KEY_HERE' \
  -d '{
    "fileId": "a1c6a2ab-4b01-4253-b4c9-70e04b3b48fc",
    "filename": "string",
    "filesize": 335226108,
    "action": "complete",
    "originalFileId": "1ebf63d7-819a-4a33-a1cd-00df81f55bd3",
    "uploadId": "gR5XHJZpuDv8UizdpSGuwONje0GbMHnCWXS5zTTVkyVINURV6iraWLhpM7Sy7oy65utAgPcm2FfM4fRp4oVga4ggEzD811aS1tke_F0iIIXX1kV7m6UouytsNE0oL8fzo2Zr2JCqwRyhFTXp98zjdQ--",
    "parts": [
      {
        "partNumber": 1,
        "etag": "6988d46a133c76f49c555deebb8efb8a"
      }
    ]
  }'

Responses

Successful operation

Bodyapplication/json
fileIdstring(uuid)
filenamestring
actionstring
Example: "Complete/Abort"
uploadIdstring
Example: "gR5XHJZpuDv8UizdpSGuwONje0GbMHnCWXS5zTTVkyVINURV6iraWLhpM7Sy7oy65utAgPcm2FfM4fRp4oVga4ggEzD811aS1tke_F0iIIXX1kV7m6UouytsNE0oL8fzo2Zr2JCqwRyhFTXp98zjdQ--"
s3Keystring
Example: "masters/843ec17f-9491-4cfa-b840-faa299973207/2-vid.mp4"
statusstring
Example: "success"
Response
application/json
{
  "fileId": "a1c6a2ab-4b01-4253-b4c9-70e04b3b48fc",
  "filename": "string",
  "action": "Complete/Abort",
  "uploadId": "gR5XHJZpuDv8UizdpSGuwONje0GbMHnCWXS5zTTVkyVINURV6iraWLhpM7Sy7oy65utAgPcm2FfM4fRp4oVga4ggEzD811aS1tke_F0iIIXX1kV7m6UouytsNE0oL8fzo2Zr2JCqwRyhFTXp98zjdQ--",
  "s3Key": "masters/843ec17f-9491-4cfa-b840-faa299973207/2-vid.mp4",
  "status": "success"
}

Assign Asset Preview Image

Request

"Generate a request to upload an image or PDF file to be the new preview for one or more Assets. Supported preview image formats include: GIF, JPG, PNG, and TIFF.\n\nIf a PDF file is uploaded to be the preview for a document Asset, then the PDF will also be displayed in the Asset Detail page as the multi-page PDF preview.\n\nAfter submitting the request to replace an Asset preview, \n\nThe user replacing the Asset previews must be granted the Replace Mezzanine and Upload User Role Permissions and View Security Template Permission on the Assets being updated.\n\nFor Federated Assets, if user provides optional contentPaths key in the request body, then files referenced in the contentPaths > properties are used as renditions."

Average Response Time: 953ms

Security
ApiKeyAuth or BasicAuth
Headers
X-API-Keystringrequired

Customer-specific API key required to invoke API.

Authorizationstringrequired

Provided by Authentication Token creation operation

Content-Typestringrequired
Value"application/json"
Bodyapplication/jsonrequired

The Request Body must be a JSON object.

fileIdsArray of strings(uuid)
Example: ["7d6f4e30-f423-11e9-8071-89c0c4052141"]
filenamestring
Example: "Preview.jpg"
filesizeinteger
Example: 1024
contentPathsobject

This property is used only for federated assets

Example: {"imagePreview":"<relativePath>","imageThumb":"<relativePath>","videoProxy":"<relativePath>"}
curl -i -X POST \
  https://api.uat.tenovos.io/v1/asset/content/preview \
  -H 'Authorization: string' \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: YOUR_API_KEY_HERE' \
  -d '{
    "fileIds": [
      "7d6f4e30-f423-11e9-8071-89c0c4052141"
    ],
    "filename": "Preview.jpg",
    "filesize": 1024,
    "contentPaths": {
      "imagePreview": "<relativePath>",
      "imageThumb": "<relativePath>",
      "videoProxy": "<relativePath>"
    }
  }'

Responses

Successful operation

Bodyapplication/jsonArray [
filenamestring

The name of the preview file to be uploaded.

Example: "Preview.jpg"
fileIdstring

The unique identifier assigned to the uploaded preview file.

Example: "b3b43fe0-17aa-4e0e-bbe3-b80c915f5508"
urlstring(URL)

Pre-signed S3 URL used to upload the preview file via a PUT request. The URL expires after a limited time.

Example: "https://1739271540099-dev-contentstore-tenovos-io.s3-accelerate.amazonaws.com/preview/b3b43fe0-17aa-4e0e-bbe3-b80c915f5508/Preview.jpg?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=EXAMPLECREDENTIAL%2F20260619%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260619T190544Z&X-Amz-Expires=86400&X-Amz-Security-Token=EXAMPLETOKEN&X-Amz-Signature=EXAMPLESIGNATURE&X-Amz-SignedHeaders=host"
]
Response
application/json
[
  {
    "filename": "Preview.jpg",
    "fileId": "b3b43fe0-17aa-4e0e-bbe3-b80c915f5508",
    "url": "https://1739271540099-dev-contentstore-tenovos-io.s3-accelerate.amazonaws.com/preview/b3b43fe0-17aa-4e0e-bbe3-b80c915f5508/Preview.jpg?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=EXAMPLECREDENTIAL%2F20260619%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260619T190544Z&X-Amz-Expires=86400&X-Amz-Security-Token=EXAMPLETOKEN&X-Amz-Signature=EXAMPLESIGNATURE&X-Amz-SignedHeaders=host"
  }
]

AUTHENTICATION

Invoke the Authentication API to generate, refresh, and revoke access tokens. An access token is required to perform any authorized API operation.

Operations

CDN (Coming Soon!)

Tenovos Content Delivery Network (CDN) - Coming Soon!

Tenovos CDN: Pull Zone Overview

Tenovos CDN provides global content acceleration and optimization through a pull zone architecture, ensuring that your assets are delivered to end users with maximum speed, reliability, and efficiency. A Content Delivery Network (CDN) works by caching static content—such as images, videos, and other media—on servers distributed across the globe. When an asset is requested, the CDN serves it from the nearest edge location, reducing load times and offloading traffic from the origin server, which in this case is Tenovos DAM.

A pull zone is the core mechanism that powers this system. It automatically fetches content from the origin the first time it is requested, then caches it at the edge. Subsequent requests are served directly from the CDN cache, improving response times and reducing bandwidth consumption.

Through the Tenovos CDN API, you can create, update, and manage pull zones programmatically. Pull zones support advanced features such as global edge caching, cache purging, bandwidth controls, and real-time performance statistics like cache hit rate and geographic request distribution. Optional optimization settings allow you to enhance performance further by enabling image compression, WebP and AVIF support, and content minification.

With just a few API calls, you can fully integrate high-performance content delivery into your Tenovos workflows—no complex infrastructure required.

Operations

COLLECTIONS

Invoke the Collection API to create, retrieve, edit, and delete Collections. Collections are used to group and catalog related Assets for quick access and consumption. Collections can be configured as:

  • private: Visible only to the user who created the Collection.
  • secured: Visible to users with.

When retrieving the Assets within a Collection, the requesting user will only see the Assets that the user has access to view. For example, a librarian may see all Assets within a Collection, but a general consumer user may only see a portion of those Assets, due to limited security access.

Operations

METADATA ATTRIBUTES

Invoke the Metadata Attributes API to retrieve Metadata Attributes, and to create, read, update, and delete Metadata Attribute definitions. Metadata Attributes come in varying types, including Text, Date, Controlled Vocabulary, Tabular, and Cascading, and can be assigned to Metadata Groups and Templates.

Admin Endpoints (NEW!): Create, read, update, and delete Metadata Attributes. These endpoints require the Metadata Management admin privilege.

Operations

METADATA GROUPS

Invoke the Metadata Groups API to create, read, update, and delete Metadata Groups. A Metadata Group organizes related Metadata Attributes together for use within a Metadata Template.

Admin Endpoints (NEW!): These endpoints require the Metadata Management admin privilege.

Operations

METADATA TEMPLATES

Invoke the Metadata Templates API to create, read, update, and delete Metadata Templates, and to apply Metadata definition changes. A Metadata Template defines a set of Metadata Attributes that, when assigned to an Asset, become available for population on that Asset.

Admin Endpoints (NEW!): Create, read, update, and delete Metadata Templates. These endpoints require the Metadata Management admin privilege.

Operations

METADATA VOCABULARIES

Invoke the Controlled Vocabularies API to create, retrieve, update, and delete Controlled Vocabularies used to constrain the values available to a Metadata Attribute.

Operations

METADATA CASCADES

Invoke the Metadata Cascades API to create, retrieve, update, and delete Cascading Attributes, a Metadata Attribute type whose available values depend on the value selected in a parent Attribute.

Operations

METADATA TABLES

Invoke the Metadata Tables API to create, retrieve, update, and delete Tabular Attributes, a Metadata Attribute type that stores structured, multi-column data on an Asset.

Operations

REQUESTS

Invoke these API's to create new Requests and manage existing Requests.

Operations

SECURITY ROLES

Invoke the Security Roles API to retrieve, create, update, and delete Security Roles, and to retrieve the Permissions and Privileges that can be assigned to a Role to control what a user can see and do across the platform.

Operations

SECURITY TEMPLATES

Invoke the Security Templates API to retrieve, create, update, and delete Security Templates. A Security Template combines Security Roles and User Groups to define access to Assets and other objects in the platform.

Operations

SECURITY GROUPS

Invoke the Security User Groups API to retrieve, create, update, and delete Security User Groups used to organize users for the purpose of assigning security access.

Operations

USERS

Invoke the User API to retrieve User profile information.

Operations

STORY BOARDS

Invoke the Story Boards API to retrieve and manage Story Boards. Story Boards are curated content experiences that combine collections, saved searches, and other content blocks into a single shareable view.

Coming Soon: Additional endpoints for creating, updating, and deleting Story Boards.

Operations

WEBHOOKS

Tenovos Webhook Subscriptions

For more information about our Webhooks, see the Webhook section of our Developer Portal

Operations

RIGHTS MANAGEMENT

Invoke the Rights Management API to manage rights-management associations between Projects, Agreements, Entities, and Rights.

Operations

PROOFING

Operations