Skip to content
Getting Started
/
/STORY BOARDS/
(COMING SOON!) List Story...

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

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

(COMING SOON!) List Story Boards

Request

🚧 Coming Soon — This endpoint is not yet available for external consumption.

Retrieve a paginated list of Story Boards. Supports cursor-based pagination, search by title/description, sorting, and filtering by publish status and locale.

Access Control:

  • Only Story Boards the user has view access to are returned
  • If the user does not have the viewStoryboards role privilege, an empty array is returned
  • Only published boards are returned unless the user has Story Board management permission
  • Permissions (canDelete, canApplySecurityTemplates, canShareInternal, canShareExternal, canPublish) are resolved server-side based on the user's role privileges and security template permissions

Pagination:

  • Uses cursor-based pagination for consistent results across large and changing lists
  • Always use the same sortBy and sortOrder values across all pages of a paginated request
  • If sort parameters change, discard the current cursor and start a new request

The user submitting the request must have the viewStoryboards role privilege.

Security
ApiKeyAuth or BasicAuth
Query
cursorstring

Cursor for pagination. Omit on the first request. Use the nextCursor value from the previous response for subsequent pages.

limitinteger<= 100

Number of results to return per page. Defaults to 50. Maximum 100.

Default 50
Example: limit=50
searchstring

Search term for filtering by title and description (partial, case-insensitive match).

Example: search=fashion
sortBystring

Field to sort by. Defaults to updatedAt.

Default "updatedAt"
Enum"updatedAt""title"
sortOrderstring

Sort direction. Defaults to desc.

Default "desc"
Enum"asc""desc"
statusstring

Filter by publish status. Defaults to all for users with management permission.

Default "all"
Enum"all""published""unpublished"
localestring

Filter by locale. Defaults to returning all locales if omitted.

Example: locale=en
Headers
Authorizationstringrequired

Bearer token from authentication.

X-API-Keystringrequired

Customer-specific API key required to invoke API.

curl -i -X GET \
  'https://api.uat.tenovos.io/v1/storyboards?cursor=string&limit=50&search=fashion&sortBy=updatedAt&sortOrder=asc&status=all&locale=en' \
  -H 'Authorization: string' \
  -H 'X-API-Key: YOUR_API_KEY_HERE'

Responses

Paginated list of Story Boards.

Bodyapplication/json
itemsArray of objects

Array of Story Board objects.

pageInfoobject

Pagination metadata.

Response
application/json
{
  "items": [
    { … },
    { … }
  ],
  "pageInfo": {
    "nextCursor": null,
    "hasNextPage": false,
    "totalCount": 2
  }
}

WEBHOOKS

Tenovos Webhook Subscriptions

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

Operations

PROOFING

Operations