Skip to content
Getting Started
/
/
/
(NEW!) Update Security Ro...

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!) Get Security Role

Request

Retrieve the full detail of a single security role, including its consent form, granted privileges, and everywhere it's currently referenced.

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

Security
ApiKeyAuth or BasicAuth
Path
idstring(uuid)required

The unique ID of the role. Opaque string, not necessarily a UUID.

Example: 6c15af83-d4a9-4772-875a-1c8a2bb1688f
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/security/roles/6c15af83-d4a9-4772-875a-1c8a2bb1688f \
  -H 'Authorization: string' \
  -H 'X-API-Key: YOUR_API_KEY_HERE'

Responses

Full detail of the security role.

Bodyapplication/json
idstring(uuid)required

Unique ID of the role.

Example: "6c15af83-d4a9-4772-875a-1c8a2bb1688f"
namestringrequired

Display name of the role.

Example: "Creative Producer"
consentFormstring

Consent text a user must accept to hold this role.

Example: "By accepting this role you agree to uphold Pied Piper's brand and confidentiality guidelines when producing creative assets."
privilegeCountinteger

Number of privileges granted to the role.

Example: 2
privilegesArray of strings(uuid)

Flat array of permitted privilege ids only. Denied/unpermitted entries in the underlying role document are not surfaced.

Example: ["31bdde6b-1a2c-4d5e-8f90-1234567890ab","9e187a4e-cfe4-419e-8c6c-2509e4bf400b"]
userCountinteger

Number of users currently assigned this role.

Example: 12
usedInobject

Everywhere the role is currently referenced.

createdBystring or null(uuid)

User-profile id of the role'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 role. 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": "6c15af83-d4a9-4772-875a-1c8a2bb1688f",
  "name": "Creative Producer",
  "consentForm": "By accepting this role you agree to uphold Pied Piper's brand and confidentiality guidelines when producing creative assets.",
  "privilegeCount": 2,
  "privileges": [
    "31bdde6b-1a2c-4d5e-8f90-1234567890ab",
    "9e187a4e-cfe4-419e-8c6c-2509e4bf400b"
  ],
  "userCount": 12,
  "usedIn": {
    "presets": [ … ]
  },
  "createdBy": "dc63db1b-1e63-43bc-877e-418931b6895c",
  "createdEpoch": 1734000000000,
  "createdDate": "2024-12-12T12:00:00.000Z",
  "lastUpdatedBy": "a5ae4577-8940-4ca9-bf2c-b1b65b4306ec",
  "lastUpdatedEpoch": 1755600000000,
  "lastUpdatedDate": "2025-08-19T12:00:00.000Z"
}

(NEW!) Update Security Role

Request

Partially update a security role. Only the fields present in the body are changed.

Business Rules:

  • At least one of name, consentForm, or privileges must be present — a body with only expectedLastUpdatedEpoch, or an empty object, is rejected with 400.
  • privileges, if supplied, fully replaces the existing set — it is not merged. An empty array clears all privileges. Omitting privileges never disturbs the stored role document.
  • Renaming to the role's own current name (even differing only by case) is not a collision.

Optimistic Concurrency:

  • expectedLastUpdatedEpoch is optional. If supplied and it doesn't match the role's current lastUpdatedEpoch, the write is rejected with 409 and code: STALE_UPDATE.

The response body is returned in the same shape as GET /security/roles/{id}.

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

Security
ApiKeyAuth or BasicAuth
Path
idstring(uuid)required

The unique ID of the role to update.

Example: 6c15af83-d4a9-4772-875a-1c8a2bb1688f
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 fields to change. At least one of name, consentForm, or privileges is required.

namestring

New display name for the role. 1-32 characters after trimming. Renaming to the role's own current name (even differing only by case) is not a collision.

Example: "Senior Compression Engineer"
consentFormstring

New consent text for the role.

Example: "By accepting this role you agree to safeguard Pied Piper's proprietary middle-out compression algorithm, follow all platform security policies, and report suspected leaks immediately."
privilegesArray of strings(uuid)

Full replacement set of privilege ids. An empty array clears all privileges. Omitting this field leaves the role's stored privileges untouched.

Example: ["31bdde6b-1a2c-4d5e-8f90-1234567890ab"]
expectedLastUpdatedEpochinteger

Optional optimistic-concurrency guard. If supplied and it doesn't match the role'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/roles/6c15af83-d4a9-4772-875a-1c8a2bb1688f \
  -H 'Authorization: string' \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: YOUR_API_KEY_HERE' \
  -d '{
    "name": "Senior Compression Engineer"
  }'

Responses

Updated. The response body is the role in the same shape as GET /security/roles/{id}.

Bodyapplication/json
idstring(uuid)required

Unique ID of the role.

Example: "6c15af83-d4a9-4772-875a-1c8a2bb1688f"
namestringrequired

Display name of the role.

Example: "Creative Producer"
consentFormstring

Consent text a user must accept to hold this role.

Example: "By accepting this role you agree to uphold Pied Piper's brand and confidentiality guidelines when producing creative assets."
privilegeCountinteger

Number of privileges granted to the role.

Example: 2
privilegesArray of strings(uuid)

Flat array of permitted privilege ids only. Denied/unpermitted entries in the underlying role document are not surfaced.

Example: ["31bdde6b-1a2c-4d5e-8f90-1234567890ab","9e187a4e-cfe4-419e-8c6c-2509e4bf400b"]
userCountinteger

Number of users currently assigned this role.

Example: 12
usedInobject

Everywhere the role is currently referenced.

createdBystring or null(uuid)

User-profile id of the role'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 role. 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": "6c15af83-d4a9-4772-875a-1c8a2bb1688f",
  "name": "Senior Compression Engineer",
  "consentForm": "By accepting this role you agree to uphold Pied Piper's brand and confidentiality guidelines when producing creative assets.",
  "privilegeCount": 1,
  "privileges": [
    "9e187a4e-cfe4-419e-8c6c-2509e4bf400b"
  ],
  "userCount": 12,
  "usedIn": {
    "presets": [ … ]
  },
  "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 Role

Request

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

Delete Rules:

  • Role must exist for the authenticated customer.
  • Deletion is blocked when either at least one user is currently assigned the role, or at least one preset (upload or filter) still references it in its role_ids. Both conditions are checked and reported together — the response names every blocker at once, not just the first one found.
  • The role is not silently unassigned from users or stripped out of presets 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 Role Management privilege.

Security
ApiKeyAuth or BasicAuth
Path
idstring(uuid)required

The unique ID of the role to delete.

Example: 6c15af83-d4a9-4772-875a-1c8a2bb1688f
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/roles/6c15af83-d4a9-4772-875a-1c8a2bb1688f \
  -H 'Authorization: string' \
  -H 'X-API-Key: YOUR_API_KEY_HERE'

Responses

No Content. The role 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