Invoke the Action API to retrieve information about invoked Actions.
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
- 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 API to retrieve Metadata Template to be applied to Assets during Asset creation. 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.
The Request Body must be a JSON object.
ID of the metadata template to apply to Request.
Array of security template IDs to apply to Request.
Metadata Attribute label/name provided by administrative user. Can be a textbox, textarea, date or dropdown.
- https://api.uat.tenovos.io/v1/request
- https://api.tenovos.io/v1/request
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
https://api.uat.tenovos.io/v1/request \
-H 'Authorization: string' \
-H 'Content-Type: application/json' \
-H 'X-API-Key: YOUR_API_KEY_HERE' \
-d '{
"title": "New Marketing Upload Request",
"metadataTemplateId": "18bb2566-0a9c-45c7-825b-4a14d3c71e42",
"securityTemplateIds": [
"1ef152a4-281a-4f02-8fb0-1204ae050705"
],
"assets": [
{
"id": "13e6991b-5c11-40b8-95ff-9e9013de44b5"
}
],
"metadata": [
{
"name": "Release Date",
"value": "01/01/2024"
},
{
"name": "Product",
"value": "HooliDocs"
},
{
"name": "Usage Table",
"value": [
[
{
"name": "Usage Category",
"value": "E-Commerce"
},
{
"name": "Usage Length",
"value": "12 months"
}
]
]
}
]
}'{ "id": "e3beae4b-338c-4fda-8bf7-be3a8d82a230" }
Request
COMING SOON!
Use this endpoint to update an existing Request. Only send the data that you wish to change.
The Request Body must be a JSON object
Email of the user to whom the assets are assigned.
- https://api.uat.tenovos.io/v1/request/{id}
- https://api.tenovos.io/v1/request/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X PATCH \
https://api.uat.tenovos.io/v1/request/4e428628-2537-40b5-91a4-5393cbf167df \
-H 'Authorization: string' \
-H 'Content-Type: application/json' \
-H 'X-API-Key: YOUR_API_KEY_HERE' \
-d '{
"assignedTo": "admin@tenovos.com",
"status": "In Progress",
"assets": [
{
"id": "cd0caff5-2756-4d7c-a43d-a926a81fa9b8",
"assignedTo": "ctc-admin@tenovos.com",
"status": "Rejected",
"note": "Test Note",
"rejectionReason": "Invalid Asset Metadata"
}
]
}'- https://api.uat.tenovos.io/v1/request/{id}
- https://api.tenovos.io/v1/request/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
https://api.uat.tenovos.io/v1/request/4e428628-2537-40b5-91a4-5393cbf167df \
-H 'Authorization: string' \
-H 'X-API-Key: YOUR_API_KEY_HERE'Success
{ "id": "e3beae4b-338c-4fda-8bf7-be3a8d82a230", "assets": [ { … } ], "assetCount": 2, "title": "Galvin's Upload Request", "type": "Upload", "status": "In Progress", "submittedBy": { "id": "556caca7-b6d4-478b-9850-bcf54b25c6b2", "firstName": "Erlich", "lastName": "Bachman", "email": "erlich.backman@piedpipper.com" }, "metadata": [ { … }, { … }, { … } ] }
Request
COMING SOON
Use this endpoint to return a listing of all Requests. The request body is entirely optional, and by default, the API will return all types of Requests sorted by created_date from the most recent to the oldest in batches of 100.
No metadata on the requests is returned from this endpoint.
The Request Body must be a JSON object.
Starting index for each request, used in conjunction with the limit property to paginate results.
Optional property to filter the response to only specific Request Types.
Optional property to filter the response to only Requests with a specific status.
- https://api.uat.tenovos.io/v1/request/list
- https://api.tenovos.io/v1/request/list
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
https://api.uat.tenovos.io/v1/request/list \
-H 'Authorization: string' \
-H 'Content-Type: application/json' \
-H 'X-API-Key: YOUR_API_KEY_HERE' \
-d '{
"from": 0,
"limit": 100,
"type": "Upload",
"status": "In Progress",
"includes": [
"asset_identifier",
"primary_sku_entry",
"pi_table_prim_product_info"
]
}'{ "total": 54, "results": [ { … } ] }
Tenovos Webhook Subscriptions
For more information about our Webhooks, see the Webhook section of our Developer Portal