Skip to content
Getting Started
/
/
/
(NEW!) Delete Metadata Te...

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

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 manage Metadata Attributes, Groups, and Templates. 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.

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

Operations

(NEW!) Update Metadata Template

Request

Partially update an existing metadata template. Only fields included in the request body will be updated — omitted fields remain unchanged.

Updatable Fields: name, groupIds, attributesDefaultValue, accessTemplates, templateOverride

Fields that cannot be updated: templateId, customerId, createdBy, createdEpoch, createdDate, templateType, templateDenormalized, dependencies

Key Business Rules:

  • Request body must contain at least one updatable field
  • Unknown or immutable fields are rejected with 400
  • name must be unique per customer (case-insensitive) — duplicate returns 409
  • groupIds must reference existing groups; system group is auto-appended last
  • Duplicate effective attributes across groups return 400
  • accessTemplates must reference existing access templates; can be cleared with []
  • attributesDefaultValue keys must exist in the effective template
  • templateDenormalized is regenerated on every successful update

The user submitting the request must have the Metadata Management admin privilege.

Security
ApiKeyAuth or BasicAuth
Path
idstring(uuid)required

The unique ID of the metadata template to update.

Example: 8cd2c221-6a91-4dc6-9379-d55dca9d5313
Headers
Authorizationstringrequired

Bearer token from authentication.

X-API-Keystring

Customer-specific API key (optional).

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

JSON object with fields to update. Only provided fields are applied.

namestring

Display name of the metadata template.

Example: "Updated Product Template"
groupIdsArray of strings(uuid)

Attribute groups included in the template. Replaces existing list.

Example: ["52ce0235-02cc-46f6-8bdb-05238c76bf83","5d1f1f87-5f64-4e03-8a2b-2c7e77f85bcb"]
attributesDefaultValueArray of objects

Default metadata values for fields in the template.

Example: [{"searchField":"title","value":"Test Assets"}]
accessTemplatesArray of strings(uuid)

Access template IDs. Pass [] to clear.

Example: []
templateOverrideobject

Template-level required/optional attribute overrides.

curl -i -X PATCH \
  https://api.uat.tenovos.io/v1/metadata/template/8cd2c221-6a91-4dc6-9379-d55dca9d5313 \
  -H 'Authorization: string' \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: YOUR_API_KEY_HERE' \
  -d '{
    "name": "Updated Product Template"
  }'

Responses

The full updated template object including regenerated templateDenormalized.

Bodyapplication/json
templateIdstring(uuid)
namestring
customerIdstring
createdBystring(uuid)
createdEpochinteger
createdDatestring(date-time)
lastUpdatedBystring(uuid)
lastUpdatedEpochinteger
lastUpdatedDatestring(date-time)
groupIdsArray of strings(uuid)
templateTypeArray of strings
attributesDefaultValueArray of objects
accessTemplatesArray of strings(uuid)
templateOverrideobject
templateDenormalizedobject

System-generated denormalized template structure.

Response
application/json
{
  "templateId": "8cd2c221-6a91-4dc6-9379-d55dca9d5313",
  "name": "Updated Asset Template",
  "customerId": "1739271540099",
  "createdBy": "dc63db1b-1e63-43bc-877e-418931b6895c",
  "createdEpoch": 1773070355217,
  "createdDate": "2026-03-11T14:32:35Z",
  "lastUpdatedBy": "dc63db1b-1e63-43bc-877e-418931b6895c",
  "lastUpdatedEpoch": 1773070399999,
  "lastUpdatedDate": "2026-03-11T15:00:00Z",
  "groupIds": [
    "52ce0235-02cc-46f6-8bdb-05238c76bf83"
  ],
  "templateType": [
    "asset"
  ],
  "attributesDefaultValue": [
    { … }
  ],
  "accessTemplates": [],
  "templateOverride": {
    "required": [ … ],
    "optional": [ … ]
  },
  "templateDenormalized": {
    "metadataGroups": [ … ]
  }
}

(NEW!) Delete Metadata Template

Request

Permanently delete a metadata template by its ID. Deletion is blocked if the template has dependencies (e.g., assets using this template).

Delete Rules:

  • Template must exist for the authenticated customer
  • Template ID must be a valid UUID
  • Template type must be one of default, asset, or action
  • Template cannot be deleted if it has dependencies (assets using it)
  • Related asset records are cleaned up
  • Deletion is recorded in tenovos_delete_history

This action is permanent and cannot be undone.

The user submitting the request must have the Metadata Management admin privilege.

Security
ApiKeyAuth or BasicAuth
Path
idstring(uuid)required

The unique ID of the metadata template to delete.

Example: e0d05152-9d1b-4b1e-bcb2-e762d195ec68
Headers
Authorizationstringrequired

Bearer token from authentication.

X-API-Keystring

Customer-specific API key (optional).

curl -i -X DELETE \
  https://api.uat.tenovos.io/v1/metadata/template/e0d05152-9d1b-4b1e-bcb2-e762d195ec68 \
  -H 'Authorization: string' \
  -H 'X-API-Key: YOUR_API_KEY_HERE'

Responses

No Content. The template has been permanently deleted.

Response
No content

Get Controlled Vocabularies

Request

Retrieve all the controlled vocabularies available to the current user.

In response, it will contain the list of metadata key/value pair and metadata definition attributes like id, name, type and search fields etc.

Average Response Time: 592ms

Security
ApiKeyAuth or BasicAuth
Headers
X-API-Keystringrequired

Customer-specific API key required to invoke API.

Authorizationstringrequired

Provided by Authentication Token creation operation

curl -i -X GET \
  https://api.uat.tenovos.io/v1/metadata/vocabulary \
  -H 'Authorization: string' \
  -H 'X-API-Key: YOUR_API_KEY_HERE'

Responses

The Response Body will be a JSON-formatted list including the following properties.

  • metadata: Vocabulary metadata
    • values: Key/Value list
      • valueId
      • valueName
    • searchable: Toggle searchability
  • metadataDefinitionId
  • metadataDefinitionName
  • metadataDefinitionSearchField: Map search field for this metadata definition
  • metadataDefinitionType: Metadata definition type
  • createdEpoch: Create time in milliseconds
  • lastUpdatedEpoch: Update time in milliseconds
Bodyapplication/jsonArray [
createdEpochinteger

Create time in milliseconds

Example: 1613877219787
customerIdstring

Customer Id

Example: "157167185123342"
lastUpdatedEpochinteger

Update time in milliseconds

Example: 1613877219787
metadataDefinitionIdstring(uuid)

Field ID

Example: "6c921f5c-24c2-40b9-8718-3ad2d4a6be54"
metadataDefinitionNamestring

Field Name

Example: "Colors"
metadataDefinitionSearchFieldstring

Map search field for this metadata definition

Example: "colors"
metadataDefinitionTypestring
Example: "controlledVocabulary"
metadataobject(ControlledVocabulary_metadata)

Vocabulary metadata

]
Response
application/json
[
  {
    "createdEpoch": 1613877219787,
    "customerId": "157167185123342",
    "lastUpdatedEpoch": 1613877219787,
    "metadataDefinitionId": "6c921f5c-24c2-40b9-8718-3ad2d4a6be54",
    "metadataDefinitionName": "Colors",
    "metadataDefinitionSearchField": "colors",
    "metadataDefinitionType": "controlledVocabulary",
    "metadata": { … }
  }
]

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

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

PROOFING

Operations