Skip to content
Getting Started
/
/
/
(NEW!) Delete Security Us...

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

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

REQUESTS

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

Operations

SECURITY

Invoke the Security API to manage Security Templates, Security Roles, Security User Groups, and the Permissions and Privileges that control what a user can see and do across the platform.

Operations

(NEW!) Rename Security User Group

Request

Rename a security user group. name is the only editable field on a group — unlike a role's PATCH, name is always required here, not "at least one of several fields."

Business Rules:

  • type is not an accepted field here either — rejected with 400.
  • Caller identity is resolved first (401 if it can't be), then the group's existence is checked (404), then the concurrency guard (if supplied), then the name-uniqueness check.
  • If the exact same name (case-sensitive) already stored is resubmitted, the request is a true no-op — no uniqueness check runs and nothing is written, including no timestamp advance. Renaming to a case-only variant of the current name (e.g. "Hooli Corporate" → "HOOLI CORPORATE") is treated as a real change and does get written.

Optimistic Concurrency:

  • expectedLastUpdatedEpoch is optional. If supplied and it doesn't match the group's current lastUpdatedEpoch, the write is rejected with 409 and code: STALE_UPDATE — checked before the name-uniqueness check, so a request that is both stale and a name collision surfaces STALE_UPDATE.

The user submitting the request must have the User Management privilege.

Security
ApiKeyAuth or BasicAuth
Path
idstringrequired

The unique ID of the group to rename.

Example: group-hooli-corporate
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 the new name. name is required.

namestringrequired

New display name for the group. 1-255 characters after trimming.

Example: "Hooli Corporate EMEA"
expectedLastUpdatedEpochinteger

Optional optimistic-concurrency guard. If supplied and it doesn't match the group's current lastUpdatedEpoch, the write is rejected with 409 and code: STALE_UPDATE.

Example: 1755600000000
curl -i -X PATCH \
  https://api.uat.tenovos.io/v1/security/user-groups/group-hooli-corporate \
  -H 'Authorization: string' \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: YOUR_API_KEY_HERE' \
  -d '{
    "name": "Hooli Corporate EMEA",
    "expectedLastUpdatedEpoch": 1755600000000
  }'

Responses

Updated. The response body is the group in the same shape as GET /security/user-groups/{id}.

Bodyapplication/json
idstringrequired

Unique ID of the group. Opaque string — ids are generated as UUIDs, but this isn't a format guarantee.

Example: "group-hooli-corporate"
namestringrequired

Display name of the group.

Example: "Hooli Corporate"
typestringrequired

Always security for a group returned by this API. Response-only — never an accepted input field on create or update.

Value"security"
Example: "security"
userCountinteger

Number of users currently in this group.

Example: 24
usedInobject

Everywhere the group is currently referenced.

createdBystring or null(uuid)

User-profile id of the group's creator. null if the row has no recorded author.

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

Unix timestamp (ms) of creation.

Example: 1734000000000
createdDatestring or null(date-time)

ISO 8601 creation date, derived from createdEpoch.

Example: "2024-12-12T12:00:00.000Z"
lastUpdatedBystring or null(uuid)

User-profile id of the last user to update the group. null if the row has no recorded author.

Example: "a5ae4577-8940-4ca9-bf2c-b1b65b4306ec"
lastUpdatedEpochinteger

Unix timestamp (ms) of the last update.

Example: 1755600000000
lastUpdatedDatestring or null(date-time)

ISO 8601 last-updated date, derived from lastUpdatedEpoch.

Example: "2025-08-19T12:00:00.000Z"
Response
application/json
{
  "id": "group-hooli-corporate",
  "name": "Hooli Corporate EMEA",
  "type": "security",
  "userCount": 24,
  "usedIn": {
    "securityTemplates": [ … ]
  },
  "createdBy": "dc63db1b-1e63-43bc-877e-418931b6895c",
  "createdEpoch": 1734000000000,
  "createdDate": "2024-12-12T12:00:00.000Z",
  "lastUpdatedBy": "a5ae4577-8940-4ca9-bf2c-b1b65b4306ec",
  "lastUpdatedEpoch": 1755600500000,
  "lastUpdatedDate": "2025-08-19T12:08:20.000Z"
}

(NEW!) Delete Security User Group

Request

Permanently delete a security user group the authenticated customer owns. There is no force-delete override — mirrors role delete.

Delete Rules:

  • Group must exist for the authenticated customer (or not be a channel-type group).
  • Deletion is blocked when either at least one user currently has this group, or at least one security template still references it. Both conditions are checked and reported together.
  • The group is not silently stripped from security templates or from users' memberships to allow the delete — the caller must resolve the blockers first.

This action is permanent and cannot be undone.

The user submitting the request must have the User Management privilege.

Security
ApiKeyAuth or BasicAuth
Path
idstringrequired

The unique ID of the group to delete.

Example: group-hooli-corporate
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/security/user-groups/group-hooli-corporate \
  -H 'Authorization: string' \
  -H 'X-API-Key: YOUR_API_KEY_HERE'

Responses

No Content. The security user group has been permanently deleted.

Response
No content

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