Invoke the Action API to retrieve information about invoked Actions.
- API v1.5 Documentation
- Payload Reference
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
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.
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.
Invoke the Metadata Attributes API to retrieve Metadata Attributes, and to create, read, update, and delete Metadata Attribute definitions. Metadata Attributes come in varying types, including Text, Date, Controlled Vocabulary, Tabular, and Cascading, and can be assigned to Metadata Groups and Templates.
Admin Endpoints (NEW!): Create, read, update, and delete Metadata Attributes. These endpoints require the Metadata Management admin privilege.
Invoke the Metadata Templates API to create, read, update, and delete Metadata Templates, and to apply Metadata definition changes. A Metadata Template defines a set of Metadata Attributes that, when assigned to an Asset, become available for population on that Asset.
Admin Endpoints (NEW!): Create, read, update, and delete Metadata Templates. These endpoints require the Metadata Management admin privilege.
Request
Retrieve a paginated, searchable list of metadata cascades for UI consumption. Response fields are lightweight by default (counts only); full level/value detail is available via GET /metadata/cascades/{id} or via the include query parameter.
Defaults:
sortFielddefaults toname.orderdefaults toasc.fromdefaults to0.limitdefaults to100— or20ifincludecontainsvalues, regardless of the value requested.
Business Rules:
searchTermis a case-insensitive partial match on cascadename.inUseaccepts a boolean (true/false— aggregate: used anywhere at all) or one ofmetadataTables,metadataGroups,metadataTemplates, filtering to cascades referenced in that specific usage category. Omitted applies no filter.inUseis also a validsortFieldvalue.includeSystemdefaults tofalse. Whentrue, also returns read-only, platform-owned cascades used internally by various platform functionalities, alongside user-created ones. System cascades cannot be edited or deleted by users.includeis a comma-separated list oflevels,values. Omitted returns summary fields only (levelCount/valueCount);include=levelsaddslevels[]per row;include=valuesaddsvalues[]per row and clampslimitto20;include=levels,valuesreturns both.usedInis shaped{ metadataTables: [], metadataGroups: [], metadataTemplates: [] }—metadataGroupsis a derived, transitive rollup through Table → group, andmetadataTemplatesa further rollup through group → template; neither is a direct reference.
The user submitting the request must have the Metadata Template Management admin privilege.
Filters by usage status. true/false filters on aggregate usage (referenced anywhere at all). One of metadataTables, metadataGroups, metadataTemplates filters to cascades referenced in that specific usage category. Omitted applies no filter.
Returns only cascades referenced directly in at least one Table.
Returns only cascades that transitively reach at least one group (Table → group) — i.e. cascades present in a group.
Returns only cascades that transitively reach at least one Template (Table → group → template).
When true, also returns read-only, platform-owned cascades used internally by various platform functionalities, in addition to user-created ones. System cascades cannot be edited or deleted by users. Defaults to false.
Number of results to return per page. Defaults to 100, maximum 100 — clamped to 20 when include contains values.
Field to sort results by. Defaults to name.
- https://api.uat.tenovos.io/v1/metadata/cascades
- https://api.tenovos.io/v1/metadata/cascades
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://api.uat.tenovos.io/v1/metadata/cascades?searchTerm=string&inUse=true&includeSystem=false&from=0&limit=100&sortField=name&order=asc&include=levels%2Cvalues' \
-H 'Authorization: string' \
-H 'X-API-Key: YOUR_API_KEY_HERE'- Default Page
- Include Values
{ "hitCount": 9, "results": [ { … } ] }
Request
Create a metadata cascade — its level schema and initial value tree — as one merged resource, in a single call. This replaces what was previously two separate writes (create the attribute, then create its value map); there is no longer a separate map/attribute split at all.
Defaults:
nameVisibledefaults totrue.
Business Rules:
levelsmust contain at most 4 entries. EachattributeIdmust reference an existing, single-select controlled-vocabulary attribute.valuesmay be omitted to create an empty cascade. Nesting depth viachildrenmust not exceedlevels.length(and therefore can never exceed 4). No two nodes in the submitted tree may share the sameid.searchFieldis optional. Omitted, it is generated server-side. Supplied, it is used as-is and the cascade is created as featured (featured: true). Either way it is permanently fixed thereafter.- A duplicate
name/searchFieldis rejected with409.
The user submitting the request must have the Metadata Template Management admin privilege.
JSON object defining the cascade to create. Required: name, levels. Optional: nameVisible (defaults to true), searchField (creates a featured cascade), values (may be omitted to create an empty cascade).
Optional. When supplied, the cascade is created as featured, using this value as its permanent search field slug instead of a server-generated one.
Whether the cascade name is visible when rendered on an asset. Defaults to true.
Level schema for the cascade. Maximum 4 entries. Each attributeId must reference an existing, single-select controlled-vocabulary attribute.
Initial value tree. May be omitted to create an empty cascade and populate values later via update. id is client-generated so a multi-level tree can be submitted in one request. Nesting depth via children must not exceed levels.length (and therefore can never exceed 4). No two nodes in the submitted tree may share the same id.
- https://api.uat.tenovos.io/v1/metadata/cascades
- https://api.tenovos.io/v1/metadata/cascades
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
- Create With Values
- Create Empty
- Create Featured
curl -i -X POST \
https://api.uat.tenovos.io/v1/metadata/cascades \
-H 'Authorization: string' \
-H 'Content-Type: application/json' \
-H 'X-API-Key: YOUR_API_KEY_HERE' \
-d '{
"name": "Region Cascade",
"nameVisible": true,
"levels": [
{
"order": 0,
"attributeId": "a29f3e1c-7b4d-4f8a-9c2e-5d1b8f6a3c70"
},
{
"order": 1,
"attributeId": "c8b6d4f2-1a3e-4c9b-8f7d-3e2a9c5b1d64"
}
],
"values": [
{
"id": "f3a8c1e5-9d24-4b7a-8e6f-1c3a9d5e2b74",
"name": "North America",
"children": [
{
"id": "7b2e9c4a-3f1d-4e8b-9a6c-5d0f2a7b3e91",
"name": "United States",
"children": []
}
]
}
]
}'Created. Returns the complete cascade detail, mirroring GET /metadata/cascades/{id}.
Ordered levels, fixed at creation. Always present here — unconditional, unlike the list endpoint where it's only included via ?include=levels.
User-profile id of the cascade's creator.
User-profile id of the last user to update the cascade.
Where the cascade is currently referenced. A cascade's only direct relationship is being used as a column inside a Table. metadataGroups is a derived, transitive rollup of every group reached through that table's own group membership (Table → group). metadataTemplates is a further derived, transitive rollup of every template reached through that group's own template membership (group → template).
Full nested value tree, returned untruncated — always present here (unconditional, same as levels; the list endpoint only includes it via ?include=values). Depth is bounded at 4 levels, but breadth is not — a level with hundreds of sibling values can still make this a large payload.
{ "id": "b7e41f2a-6c9d-4a17-8f3b-2d5c8a0e3f61", "name": "Region Cascade", "searchField": "region_cascade", "levels": [ { … } ], "nameVisible": true, "featured": true, "createdBy": "8f2a5c91-4e6d-4b83-9a17-6c0d3e8b2f45", "createdEpoch": 1770714900000, "createdDate": "2026-02-10T09:15:00Z", "lastUpdatedBy": "8f2a5c91-4e6d-4b83-9a17-6c0d3e8b2f45", "lastUpdatedEpoch": 1770714900000, "lastUpdatedDate": "2026-02-10T09:15:00Z", "usedIn": { "metadataTables": [], "metadataGroups": [], "metadataTemplates": [] }, "values": [] }
Request
Retrieve a single metadata cascade by its ID. This is the one place in the cascades API where everything is always returned unconditionally — no include option, no summary/lightweight mode.
The user submitting the request must have the Metadata Template Management admin privilege.
- https://api.uat.tenovos.io/v1/metadata/cascades/{id}
- https://api.tenovos.io/v1/metadata/cascades/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
https://api.uat.tenovos.io/v1/metadata/cascades/b7e41f2a-6c9d-4a17-8f3b-2d5c8a0e3f61 \
-H 'Authorization: string' \
-H 'X-API-Key: YOUR_API_KEY_HERE'The requested metadata cascade.
Ordered levels, fixed at creation. Always present here — unconditional, unlike the list endpoint where it's only included via ?include=levels.
User-profile id of the cascade's creator.
User-profile id of the last user to update the cascade.
Where the cascade is currently referenced. A cascade's only direct relationship is being used as a column inside a Table. metadataGroups is a derived, transitive rollup of every group reached through that table's own group membership (Table → group). metadataTemplates is a further derived, transitive rollup of every template reached through that group's own template membership (group → template).
Full nested value tree, returned untruncated — always present here (unconditional, same as levels; the list endpoint only includes it via ?include=values). Depth is bounded at 4 levels, but breadth is not — a level with hundreds of sibling values can still make this a large payload.
{ "id": "b7e41f2a-6c9d-4a17-8f3b-2d5c8a0e3f61", "name": "Region Cascade", "searchField": "region_cascade", "levels": [ { … }, { … } ], "nameVisible": true, "featured": null, "createdBy": "8f2a5c91-4e6d-4b83-9a17-6c0d3e8b2f45", "createdEpoch": 1770714900000, "createdDate": "2026-02-10T09:15:00Z", "lastUpdatedBy": "8f2a5c91-4e6d-4b83-9a17-6c0d3e8b2f45", "lastUpdatedEpoch": 1771432800000, "lastUpdatedDate": "2026-02-18T16:40:00Z", "usedIn": { "metadataTables": [ … ], "metadataGroups": [ … ], "metadataTemplates": [ … ] }, "values": [ { … } ] }
Request
Update an existing cascade's name, nameVisible, and/or its full value tree. levels and featured can never be changed through this endpoint — levels because restructuring which attributes back a level could invalidate the existing value tree, and featured because it exists specifically to protect a cascade from deletion and would mean nothing if it could simply be toggled off here.
Business Rules:
- At least one of
name,nameVisible,valuesis required. - When
valuesis provided, it fully replaces the existing tree — nodes omitted from the request are removed. Same depth and duplicate-idrules as create. usedInis not enforced or checked on this endpoint — a value may be updated or removed even while referenced on assets; asset reconciliation is handled by a separate downstream process, out of scope here.- A new
namecolliding with an existing cascade'sname/searchFieldis rejected with409. - An optional
expectedLastUpdatedEpochconcurrency check protects against clobbering another admin's concurrent edit. If it doesn't match the cascade's currentlastUpdatedEpoch, the request is rejected with409and the response includescurrentLastUpdatedEpoch.
The user submitting the request must have the Metadata Template Management admin privilege.
JSON object updating the cascade. At least one of name, nameVisible, values is required. levels and featured are never accepted.
Full replacement of the value tree — not a diff. Nodes omitted from the request are removed. Same shape, depth, and duplicate-id rules as create.
- https://api.uat.tenovos.io/v1/metadata/cascades/{id}
- https://api.tenovos.io/v1/metadata/cascades/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
- Update Values
- Rename Cascade
curl -i -X PATCH \
https://api.uat.tenovos.io/v1/metadata/cascades/b7e41f2a-6c9d-4a17-8f3b-2d5c8a0e3f61 \
-H 'Authorization: string' \
-H 'Content-Type: application/json' \
-H 'X-API-Key: YOUR_API_KEY_HERE' \
-d '{
"expectedLastUpdatedEpoch": 1771432800000,
"values": [
{
"id": "f3a8c1e5-9d24-4b7a-8e6f-1c3a9d5e2b74",
"name": "North America",
"children": [
{
"id": "7b2e9c4a-3f1d-4e8b-9a6c-5d0f2a7b3e91",
"name": "United States",
"children": []
},
{
"id": "1c9a4e7f-6b3d-4a25-8f7c-2e9b5d1a4c63",
"name": "Canada",
"children": []
}
]
}
]
}'Updated. Returns the complete cascade detail, mirroring GET /metadata/cascades/{id}, reflecting the values tree exactly as it now stands.
Ordered levels, fixed at creation. Always present here — unconditional, unlike the list endpoint where it's only included via ?include=levels.
User-profile id of the cascade's creator.
User-profile id of the last user to update the cascade.
Where the cascade is currently referenced. A cascade's only direct relationship is being used as a column inside a Table. metadataGroups is a derived, transitive rollup of every group reached through that table's own group membership (Table → group). metadataTemplates is a further derived, transitive rollup of every template reached through that group's own template membership (group → template).
Full nested value tree, returned untruncated — always present here (unconditional, same as levels; the list endpoint only includes it via ?include=values). Depth is bounded at 4 levels, but breadth is not — a level with hundreds of sibling values can still make this a large payload.
{ "id": "b7e41f2a-6c9d-4a17-8f3b-2d5c8a0e3f61", "name": "Global Region Cascade", "searchField": "region_cascade", "levels": [ { … }, { … } ], "nameVisible": false, "featured": null, "createdBy": "8f2a5c91-4e6d-4b83-9a17-6c0d3e8b2f45", "createdEpoch": 1770714900000, "createdDate": "2026-02-10T09:15:00Z", "lastUpdatedBy": "8f2a5c91-4e6d-4b83-9a17-6c0d3e8b2f45", "lastUpdatedEpoch": 1773480000000, "lastUpdatedDate": "2026-09-05T11:20:00Z", "usedIn": { "metadataTables": [], "metadataGroups": [], "metadataTemplates": [] }, "values": [ { … } ] }
Request
Permanently remove a metadata cascade. Deletion is blocked if the cascade is featured, and blocked if it is still referenced by a table (and, transitively, any template that reaches it through that table).
Business Rules:
- Checks run in this order: not found, then featured, then in-use.
The user submitting the request must have the Metadata Template Management admin privilege.
- https://api.uat.tenovos.io/v1/metadata/cascades/{id}
- https://api.tenovos.io/v1/metadata/cascades/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X DELETE \
https://api.uat.tenovos.io/v1/metadata/cascades/b7e41f2a-6c9d-4a17-8f3b-2d5c8a0e3f61 \
-H 'Authorization: string' \
-H 'X-API-Key: YOUR_API_KEY_HERE'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.
Tenovos Webhook Subscriptions
For more information about our Webhooks, see the Webhook section of our Developer Portal