Does my shop need an interface to TESSA?

No. Path and preset follow your naming conventions, so your shop builds the image URL itself — with no asset ID and no extra interface.

What is a delivery URL made of?

Three parts: your TESSA address, the asset — by short ID or by folder and file name — and the transformation, either as a preset name or as the operations themselves.

How do images reach partners who have no TESSA access?

Through a link with an expiry date that you send by email or chat. For recurring handovers you set up export channels with fixed formats; systems without a user interface fetch the files through the REST API.

All features

Delivery URLs

Image URLs your shop builds itself

Every image gets a URL for your preset, built from three parts: your TESSA address, the asset — by short ID or by folder and file name — and the transformation: the preset name, so TESSA defines the output, or the operations themselves, so your shop decides. Path and preset follow your naming conventions, so your shop builds the URL itself: no asset ID, no extra interface.

Three parts, one URL
Your TESSA address, the asset and the transformation: that is all an image URL needs.
Short ID or path
Address the image by its short ID or simply by folder and file name, the way your shop already knows it.
Preset or operations
With the preset name, TESSA defines the output. With the operations themselves, your shop decides.
No extra interface
Path and preset follow your naming conventions. For another image only the asset part changes, no asset ID lookup.