Assets

Uploading binaries and managing the asset records that reference them.

Examples assume a configured IManagementClient client — see configuration.

• Upload and create an asset
• Supported sources and ownership
• Separate upload from asset creation
• Update metadata and organize assets

Upload and create an asset

An asset is a binary file plus its metadata, and creating one is two operations: upload the file, then create the asset referencing it. The CreateAssetAsync(FileContentSource, Func<FileReference, AssetCreateModel>) extension does both, handing your factory the FileReference the upload produced:

using Kontent.Ai.Management.Extensions;

var result = await client.CreateAssetAsync(
    new FileContentSource(File.ReadAllBytes("chart.png"), "chart.png", "image/png"),
    fileReference => new AssetCreateModel
    {
        FileReference = fileReference,
        Title = "Roasting chart"
    });

If the upload fails, no asset is created and the upload's failure is returned.

UpsertAssetAsync(identifier, FileContentSource, AssetUpsertModel) is the create-or-update counterpart.

Assets can carry taxonomy terms, using the asset-type elements defined on the environment. That needs schema that exists in your environment, so it is not part of a minimal upload:

Elements =
[
    new AssetTaxonomyElement
    {
        Element = Reference.ByCodename("taxonomy-categories"),
        Value = [Reference.ByCodename("hello"), Reference.ByCodename("sdk")]
    }
]

Supported sources and ownership

The upload endpoint needs the file size up front, so FileContentSource accepts only sources that can report one.

Source	Who disposes the stream	On a retry
byte[]	the SDK — it opens and disposes one per attempt	a fresh stream each attempt
file path	the SDK — same	a fresh stream each attempt
Stream	you — the SDK never disposes it	rewound to position 0 and replayed

This is also what makes every upload safe to retry: whichever source you choose, a 429 retry re-sends the same bytes rather than a truncated body.

Uploads have no per-attempt timeout by default, and the whole call is bounded by ManagementOptions.Timeout — see retries and timeouts.

Separate upload from asset creation

Call the two steps yourself when you want finer control — reusing one uploaded file across several assets, for instance:

var fileReference = (await client.UploadFileAsync(
    new FileContentSource(File.ReadAllBytes("chart.png"), "chart.png", "image/png"))).EnsureSuccess();

var result = await client.CreateAssetAsync(new AssetCreateModel
{
    FileReference = fileReference,
    Title = "Roasting chart"
});

Update metadata and organize assets

Task	Method
List assets	ListAssetsAsync, ListAssetsPageAsync
Get one	GetAssetAsync
Update metadata, or create-or-update	UpsertAssetAsync
Delete	DeleteAssetAsync
Renditions	CreateAssetRenditionAsync, ListAssetRenditionsAsync, GetAssetRenditionAsync
Folder hierarchy	GetAssetFoldersAsync, CreateAssetFoldersAsync, ModifyAssetFoldersAsync

Asset listings can grow large, so they have page overloads — see pagination.

Transforming an image for delivery — resizing, cropping, format — is the Delivery SDK's job, not this one.