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

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 Group

Request

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

When attributeIds is provided, the existing attribute list is fully replaced in the order given.

Fields that cannot be updated: searchField.

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 group to update.

Example: 52ce0235-02cc-46f6-8bdb-05238c76bf83
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

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

namestring

Updated display name of the group.

Example: "Updated Group Name"
attributeIdsArray of strings(uuid)

Updated ordered list of attribute IDs. Replaces the existing list entirely. Order is preserved.

Example: ["01dc8715-c660-44cb-b3a4-70f4779e6651","013ad220-b377-432d-bc6d-b1614dbb82c1"]
isGroupNameVisibleboolean

Whether the group name is visible when rendered on an asset.

Example: true
curl -i -X PATCH \
  https://api.uat.tenovos.io/v1/metadata/group/52ce0235-02cc-46f6-8bdb-05238c76bf83 \
  -H 'Authorization: string' \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: YOUR_API_KEY_HERE' \
  -d '{
    "name": "Updated Group Name"
  }'

Responses

The full updated group object with resolved attributes.

Bodyapplication/json
idstring(uuid)

Unique ID of the group.

Example: "52ce0235-02cc-46f6-8bdb-05238c76bf83"
namestring

Display name of the group.

Example: "Product Information"
searchFieldstring

System-generated slug derived from the group name. Immutable after creation.

Example: "product_information"
customerIdstring

ID of the customer/tenant.

Example: "1739271540099"
createdBystring(uuid)

UUID of the user who created the group.

Example: "dc63db1b-1e63-43bc-877e-418931b6895c"
createdEpochinteger

Creation timestamp in Unix milliseconds.

Example: 1773070355217
createdDatestring(date-time)

Human-readable creation date in ISO 8601 format.

Example: "2026-03-20T12:05:27Z"
lastUpdatedBystring(uuid)

UUID of the user who last updated the group.

Example: "dc63db1b-1e63-43bc-877e-418931b6895c"
lastUpdatedEpochinteger

Last updated timestamp in Unix milliseconds.

Example: 1773070355217
lastUpdatedDatestring(date-time)

Human-readable last updated date in ISO 8601 format.

Example: "2026-03-20T12:05:27Z"
isGroupNameVisibleboolean

Whether the group name is visible when rendered on an asset.

Example: false
usedInobject

Describes where the group is currently referenced. Present on GET by ID responses.

attributesArray of objects

Ordered list of attributes in the group.

Response
application/json
{
  "id": "52ce0235-02cc-46f6-8bdb-05238c76bf83",
  "name": "Updated Group Name",
  "searchField": "product_information",
  "customerId": "1739271540099",
  "createdBy": "dc63db1b-1e63-43bc-877e-418931b6895c",
  "createdEpoch": 1773070355217,
  "createdDate": "2026-03-20T12:05:27Z",
  "lastUpdatedBy": "dc63db1b-1e63-43bc-877e-418931b6895c",
  "lastUpdatedEpoch": 1773070399999,
  "lastUpdatedDate": "2026-03-20T13:00:00Z",
  "isGroupNameVisible": false,
  "usedIn": {
    "metadataTemplates": [ … ]
  },
  "attributes": [
    { … },
    { … },
    { … },
    { … }
  ]
}

(NEW!) Delete Metadata Group

Request

Permanently delete a metadata group by its ID. Deletion is blocked if the group is currently referenced by any metadata template.

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 group to delete.

Example: 52ce0235-02cc-46f6-8bdb-05238c76bf83
Headers
X-API-Keystringrequired

Customer-specific API key required to invoke API.

Authorizationstringrequired

Provided by Authentication Token creation operation.

curl -i -X DELETE \
  https://api.uat.tenovos.io/v1/metadata/group/52ce0235-02cc-46f6-8bdb-05238c76bf83 \
  -H 'Authorization: string' \
  -H 'X-API-Key: YOUR_API_KEY_HERE'

Responses

No Content. The group has been permanently deleted.

Response
No content

Retrieve Metadata Templates

Request

Retrieve all metadata templates available to the requesting user

The user submitting the request must have administrator rights to view metadata templates.

Average Response Time: 492ms

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"
curl -i -X GET \
  https://api.uat.tenovos.io/v1/metadata/template \
  -H 'Authorization: string' \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: YOUR_API_KEY_HERE'

Responses

The Response Body will be a JSON array of template objects.

Bodyapplication/jsonArray [
templateobject(MetadataTemplate_template)
]
Response
application/json
[
  {
    "template": { … }
  }
]

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