Skip to content
Getting Started
/
/
/
(NEW!) Update an Asset

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
  • We've made some performance improvements to most endpoints
Find out more about Tenovos
Download OpenAPI description
v1.5.json
v1.5.yaml
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

(NEW!) Retrieve an Asset

Request

Retrieves an asset's details and metadata by specifying an Asset Identifier or File Identifier in the request path.

** The user requesting the Asset must have view access to the Asset. **

Security
ApiKeyAuth or BasicAuth
Path
idstring(uuid)required

The Asset Identifier (same as objectId) to retrieve.

Query
emptyboolean

Default is true. When false, results will not include metadata without values, when true all metadata attributes for the asset will be returned even those with no values provided.

systemboolean

Default is true. When false, system metadata fields will be excluded from the metadata array that is returned in the response.

Headers
X-API-Keystringrequired

Customer-specific API key required to invoke API.

Authorizationstringrequired

Provided by Authentication Token creation operation

Content-Typestringrequired
Value"application/json"
curl -i -X GET \
  'https://api.uat.tenovos.io/v1/assets/asset/{id}' \
  -H 'Authorization: string' \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: YOUR_API_KEY_HERE'

Responses

Success

Bodyapplication/json
statusstring

Response Status indicator returned by Tenovos

Example: "success"
messagestring

Message indicated whether the asset was successfully created or not.

Example: "Asset created successfully"
dataobject
Response
application/json
{
  "status": "success",
  "message": "Asset created successfully",
  "data": {
    "createdDate": "2024-06-10T12:13:23.782Z",
    "lastUpdatedDate": "2024-07-12T18:42:01.102Z",
    "fileId": "0fcb5eb4-5e0e-4ffa-8780-9206a0f833f1",
    "filename": "hooli-logo.jpg",
    "fileSizeInBytes": 209743,
    "originalFileId": "0fcb5eb4-5e0e-4ffa-8780-9206a0f833f1",
    "createdBy": "ffc1f0c6-3a6d-474d-8e24-3ccda6be27a2",
    "lastUpdatedBy": "ffc1f0c6-3a6d-474d-8e24-3ccda6be27a2",
    "assetId": "2dee909b-6b2b-4da8-96c3-af90fc1662ec",
    "type": "Asset",
    "currentVersion": true,
    "versionNumber": 1718021603782,
    "AITags": [ … ],
    "metadataState": "available",
    "metadataTemplateId": "ea6eb24d-adef-4380-bd02-f64f567c437f",
    "renditionsDocument": { … },
    "fileState": "available",
    "securityTemplateIds": [ … ],
    "avamTags": [ … ],
    "lockType": [ … ],
    "metadata": [ … ]
  }
}

(NEW!) Update an Asset

Request

Update the metadata attribute values and/or the Security Template assignments for an Asset identified by Object ID (Asset ID). ** The identifier must be specified in the path parameter.

** The user requesting the Asset must have edit role privilege, as well as edit permission on the Asset's security template in order to update the Asset. **

Security
ApiKeyAuth or BasicAuth
Path
idstring(uuid)required

The Asset Identifier belonging to the Asset to update.

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/json

The Request Body must be a JSON object. Update the security templates assigned to an Asset, or update metadata values. Only those values you wish to change need to be provided.

securityTemplateIdsArray of strings(uuid)[ 1 .. 50 ] items
Example: ["b84ac1dc-30ed-4741-8f8d-47ef2635950b"]
metadataArray of attribute (object) or table (object)
Example: [{"name":"Release Date","value":"01/01/2024"},{"name":"Product","value":"HooliDocs"},{"name":"Usage Table","value":[[{"name":"Usage Category","value":"E-Commerce"},{"name":"Usage Length","value":"12 months"}],[{"name":"Usage Category","value":"Physical Retail"},{"name":"Usage Length","value":"18 months"}],[{"name":"Usage Category","value":"Social Media"},{"name":"Usage Length","value":"6 months"}]]}]
curl -i -X PATCH \
  'https://api.uat.tenovos.io/v1/assets/asset/{id}' \
  -H 'Authorization: string' \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: YOUR_API_KEY_HERE' \
  -d '{
    "securityTemplateIds": [
      "b84ac1dc-30ed-4741-8f8d-47ef2635950b"
    ],
    "metadata": [
      {
        "name": "Release Date",
        "value": "01/01/2024"
      },
      {
        "name": "Product",
        "value": "HooliDocs"
      },
      {
        "name": "Usage Table",
        "value": [
          [
            {
              "name": "Usage Category",
              "value": "E-Commerce"
            },
            {
              "name": "Usage Length",
              "value": "12 months"
            }
          ],
          [
            {
              "name": "Usage Category",
              "value": "Physical Retail"
            },
            {
              "name": "Usage Length",
              "value": "18 months"
            }
          ],
          [
            {
              "name": "Usage Category",
              "value": "Social Media"
            },
            {
              "name": "Usage Length",
              "value": "6 months"
            }
          ]
        ]
      }
    ]
  }'

Responses

Success

Bodyapplication/json
One of:
statusstring

Response Status indicator returned by Tenovos

Example: "success"
messagestring

Message indicated whether the asset was successfully created or not.

Example: "Asset Update was successful"
Response
application/json
{
  "status": "success",
  "message": "Asset Update was successful"
}

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

Invoke the Metadata API to retrieve Metadata Template to be applied to Assets during Asset creation. A Metadata Template defines a set of Metadata Attributes of varying types, including Text, Date, Controlled Vocabulary, Tabular, and Cascading Attributes. When a Metadata Template is assigned to a new Asset, the corresponding Metadata Attributes will be available for population on the Asset.

Operations

REQUESTS

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

Operations

SECURITY

Invoke the Metadata API to retrieve Security Template information to be applied to Assets during Asset creation or edit.

Operations

PEOPLE

Invoke the User API to retrieve User profile information.

Operations

WEBHOOKS

Tenovos Webhook Subscriptions

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

Operations

PROOFING

Operations