Project Assets

Project Asset Management

Manage assets (images, videos, documents, and other files) associated with translation segments. This API enables uploading, downloading, listing, and deleting assets that provide visual context or reference materials for translators and reviewers.

Overview

The Assets API allows you to attach files to specific segments within projects or jobs. Assets are stored in the project's reference material folder and can be organized using relative paths for better file management. This feature is particularly valuable for game localization, CMS integrations, and any translation workflow where visual context enhances translation quality.

Key Features

File Upload: Upload assets to specific segments with support for various file types
Organized Storage: Use relative paths to organize files in folders within segment directories
Multi-language Support: Associate assets with specific locales or keep them language-neutral
Bulk Operations: List assets across multiple segments efficiently
Access Control: Proper permission checking based on project reference material access rights

Storage Structure

Assets are stored following this hierarchical structure:

CODE

{reference material}/assets/{document ID}/{segment ID % 1000}/{segment ID}/

With locale-specific storage:

CODE

{reference material}/assets/{document ID}/{segment ID % 1000}/{segment ID}/{locale}/

With relative paths:

CODE

{reference material}/assets/{document ID}/{segment ID % 1000}/{segment ID}/{locale}/{relativePath}/

Available Endpoints

Method	Endpoint	Description
POST	`/resources/assets/{segmentid}`	Upload asset to segment
GET	`/resources/assets/{segmentid}`	Download specific asset
GET	`/resources/assets/{segmentid}/list`	List all assets in segment
GET	`/resources/assets/list`	List assets for multiple segments
DELETE	`/resources/assets/{segmentid}`	Delete specific asset or all assets in segment

Prerequisites

Before uploading assets, files must first be uploaded using the media upload API:

CODE

POST /api/media/upload?filename={filename}

This returns a filetoken that is then used in the asset upload request.

File Path Flexibility

The API supports flexible file organization:

Via Parameter: Use the relativePath parameter to specify folder structure
Via Filename: Include the path directly in the filename (e.g., "images/screenshot.jpg")
Precedence: When both are provided, relativePath takes precedence

Access Rights

Users must have appropriate access rights to the project's reference material to perform asset operations. The system automatically validates permissions based on the specified scope and user privileges.